[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] GNUmed 1.5.0 Feature Release

From: Busser, Jim
Subject: Re: [Gnumed-devel] GNUmed 1.5.0 Feature Release
Date: Wed, 28 Jan 2015 14:11:30 +0000

On 2015-01-08, at 8:01 AM, Karsten Hilbert <address@hidden> wrote:

> Hello all,
> I am glad to be able to announce the immediate availability
> of the GNUmed 1.5.0 Feature Release. It provides the
> following bug fixes and improvements:
> Changelog:
>       ...
>       IMPROVED: enhance dynamic keyword text expansions

I have created

and think it's mostly correct. I am only not yet sure whether I understood 
correctly, from archival -devel postings

1) whether I got it right that, in the case where the key word matches two or 
more expansions, the user would be offered their choice?

2) in what situations this arises … are we talking two expansions having the 
same last word?

3) can this also arise where two expansions share a last word "part" combined 
with a "match search" that has been activated manually by Control-M rather than 
by an end-of-word character?

4) must the keyword be a single uninterrupted string whose words, if 
semantically multiple, need to be 'bound' by (for example) - or _ ?

5) any situations outside of document descriptions where a single-line text 
field might access a multi-line expansion one of whose lines having then to be 

-- Jim

reply via email to

[Prev in Thread] Current Thread [Next in Thread]