[Pkg-jed-commit] r781 - in jed/branches/0.99.19/debian: . patches

[G. Milde]

On 19.06.07, Jörg Sommer wrote:

>   · Integrated the FAQ from README.Debian into jed_faq,

Thanks Jörg.

>     I didn't include the answers A3 and A4, and the questions ???TAB does not
>     generate a TAB??? (it's already in jed_faq), ???My colour scheme does not
>     work??? (I don't consider this as a common question) and ???Everything broke
>     with SLang 2??? (SLang 2 is in stable, I don't think we should care about
>     this upgrade anymore.)

This is all right.

>   · Updated the date in the copyright line.

You might have updated the last line, which still reads

>     Last update 2007-01-18 Guenter Milde

.


Could we keep Answer 4 to the "staircase-question"? IMO, this is the easiest
solution (once set up) as you can work as if nothing special happened.

> ++  The reason, why this happens is:
> ++  In Jed, carriage return is bound to `newline_and_indent'. While this
> ++  auto-indention is a great help in normal editing, it stands in the way when
> ++  text is pasted via the mouse. Unfortunately, Jed cannot tell whether its
> ++  input comes from a keyboard, another program, or the mouse (XJed can).
> ++
> ++  There is more than one answer how you can prevent it:
> ++  1: Use xjed.
> ++  2: Use the `paste' function
> ++      1. M-x paste  (or bind "paste" to a key)
> ++      2. Now paste your text...
> ++  3: Temporarily change the keybinding by doing:
> ++      1. M-X local_setkey("newline","^M") (Alt-Shift-X: the S-Lang prompt)
> ++      3. Now paste your text...
> ++      4. M-X local setkey("newline_and_indent","^M")

++  4: Use the fact that Jed can tell whether there is input pending after the
++     carriage return. Define in your jed.rc (or any other file evaluated at
++     startup):
++          public define newline_indent ()
++          {
++            if (input_pending(0))
++               newline();
++            else
++               call ("newline_and_indent");
++          }
++          setkey("newline_indent","^M");
++     On a slow terminal (remote login or heavy load) this might fail by
++     non-indenting after fast typing of CR and the first character of the new
++     line.


Guenter