On Sat, Oct 07, 2006 at 10:45:13PM +0200, Axel Liljencrantz wrote:
the fish syntax needs
to be changed so that a backslash before a newline is ignored even
when inside quotes, which is not the case today.
what does that mean?
Once the history problem is fixed, the new config file reshuffle
On 10/8/06, Martin Bähr [EMAIL PROTECTED] wrote:
On Sat, Oct 07, 2006 at 10:45:13PM +0200, Axel Liljencrantz wrote:
the fish syntax needs
to be changed so that a backslash before a newline is ignored even
when inside quotes, which is not the case today.
what does that mean?
Currently, a
On 10/6/06, Axel Liljencrantz [EMAIL PROTECTED] wrote:
On 10/6/06, Beni Cherniavsky [EMAIL PROTECTED] wrote:
[...]
Not necessarily. The terminal stores a hidden bit at every end of
line, rememebering whether it was crossed by wrapping a long text.
I'm not sure what's the exact rule that
On 10/5/06, Axel Liljencrantz [EMAIL PROTECTED] wrote:
On 10/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Multiline editing rocks. Here are some thoughts.
The ellipsis (…) at the start and end of lines is cool and makes clear
that the line was wrapped. But it also complicates pasting
Hurray for multiline editing!
Is it possible to make it indent right after moving to the new line,
rather than waiting for the first character to be typed? Then the
cursor would not need to be moved again, unless the user types end,
which is unlikely. This will make it clearer to the user
