Re: More patches

["G. Milde" <milde@xxxxxxxxxxxxxxxxxxxxx>]

On 19.05.08, J�rg Sommer wrote:
> Hi again,

> diff -urNad 0.99.19~/doc/tm/rtl/mini.tm 0.99.19/doc/tm/rtl/mini.tm

> -  error can be caught by an \var{ERROR_BLOCK} and the appropriate action
> +  error can be caught by a \var{try-catch} statement and the appropriate action

Should be ``\var{try} - \var{catch}`` statement, as try and catch arr S-Lang
keywords that should be marked (like ERROR_BLOCK in the old version).


> http://git.debian.org/?p=pkg-jed/jed.git;a=blob;hb=jo-0.99.19;f=debian/patches/extend-help.sl.dpatch

>     * Improves expand_keystring() to return Alt- instead of ESC, if ALT_CHAR
>       is non-zero, and print Space instead of the space character

Please test for ALT_CHAR == 27 instead of != 0:

 DESCRIPTION
  If this variable is non-zero, characters pressed in combination the
  `Alt' key will generate a two character sequence: the first
  character is the value of `ALT_CHAR' itself followed by the
  character pressed.  For example, if `Alt-X' is pressed and
  `ALT_CHAR' has a value of 27, the characters `ESC X' will be
  generated.


> http://git.debian.org/?p=pkg-jed/jed.git;a=blob;hb=jo-0.99.19;f=debian/patches/remove_jed_library_path.dpatch

>     In version 0.99.19-82 the require and provides functions where dropped
>     from jed and the functions from slsh stepped in. They have a different
>     argument list than the old jed functions and they do not care about jed
>     library path. So it's time to kick the jed library path and replace it
>     slang load path.
>       This patch includes two SLang function [gs]et_jed_library_path() as
>     wrapper around [gs]et_slang_load_path() to ease migratition.

Sounds a lot like incompatible with jed-extra. --> if so, and if we are
going to upload 0.99 to unstable, it should conflict with the current
jed-extra version.

Günter

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.