Set Terminal settings to use the alt/option key as alt.
On Fri, Mar 26, 2010 at 2:14 AM, i...@whywouldwe.com wrote:
> To get a new line the docs say "Pressing Alt-enter instead of pressing
> the enter key".
>
> Macs don't have an alt key and I've tried all the combinations I can
> think of, does
To get a new line the docs say "Pressing Alt-enter instead of pressing
the enter key".
Macs don't have an alt key and I've tried all the combinations I can
think of, does anyone know a way to get a new line other than \ and enter?
Thanks
---
On 2/26/07, Mike Roberts <[EMAIL PROTECTED]> wrote:
> there's a couple of problems with the multiline mode of the editor:
>
> * when my command line spills onto the next line, an ellipsis is put on
> the second line and i get another ellipsis on the third line that's
> indented. is the intent to ha
there's a couple of problems with the multiline mode of the editor:
* when my command line spills onto the next line, an ellipsis is put on
the second line and i get another ellipsis on the third line that's
indented. is the intent to have the first ellipsis complete the first
line?
* subsequen
On 10/16/06, Ben Stiglitz <[EMAIL PROTECTED]> wrote:
>
>
>
> Ah, I understand. Unfortunatly, it seems that allowing the terminal to
>
> wrap itself makes cursor movement unpredictable. Sometimes moving
>
> up/down the wrapped line is seen as one line, sometimes as two.
> That would definitely be a
Ah, I understand. Unfortunatly, it seems that allowing the terminal to wrap itself makes cursor movement unpredictable. Sometimes moving up/down the wrapped line is seen as one line, sometimes as two. That would definitely be a bug in your terminal emulator or your cursor handling code. While many
On 10/15/06, Beni Cherniavsky <[EMAIL PROTECTED]> wrote:
> On 09/10/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> > * When selecting wrapped text with the mouse, the 'wrapping
> > characters' are also copied. It would be cool if they could be made to
> > magically disapear, as Beni suggested m
On 09/10/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> * When selecting wrapped text with the mouse, the 'wrapping
> characters' are also copied. It would be cool if they could be made to
> magically disapear, as Beni suggested might be possible. Note that
> other programs, like emacs, don't d
On 10/9/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> 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 an
On 10/9/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> 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 cross
On 10/9/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> 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",
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 what
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 complic
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 ru
On 10/6/06, Beni Cherniavsky <[EMAIL PROTECTED]> wrote:
> On 05/10/06, Philip Ganchev <[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 complicate
On 10/6/06, Beni Cherniavsky <[EMAIL PROTECTED]> wrote:
> On 05/10/06, Philip Ganchev <[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 complicate
On 05/10/06, Philip Ganchev <[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 commands
> into an editor, as you have to delete all the
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 commands
> into an editor, as you have to delete all t
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 commands
into an editor, as you have to delete all the ellipses. Granted,
pasting would require re-formatting anyway
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 commands
into an editor, as you have to delete all the ellipses. Granted,
pasting would require re-formatting anyway
On 10/1/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> I've finally gotten around to taking a first stab at
> multiline editing. There is a patch in the darcs tree
> that enables this.
Awesome! This is very exciting!
> Features:
>
> * Single-line editing works as before. There should be
> no
--- Martin Bähr <[EMAIL PROTECTED]>
skrev:
[...]
> ps: there seems to be a gmail->sourceforge problem,
> as myrddin also
> can't write to the list.
Yup. Very silly indeed. Hope they get this sorted out
soon.
[...]
--
Axel
-
--- Philip Ganchev <[EMAIL PROTECTED]> skrev:
> On 10/1/06, Axel Liljencrantz
> <[EMAIL PROTECTED]> wrote:
> > I've finally gotten around to taking a first stab
> at
> > multiline editing. There is a patch in the darcs
> tree
> > that enables this.
>
> Awesome! This is very exciting!
>
> > Fea
--- Martin Bähr <[EMAIL PROTECTED]>
skrev:
> On Sun, Oct 01, 2006 at 06:12:10PM +0200, Axel
> Liljencrantz wrote:
> > * The current history file format can't support
> multiline commands
> > stored as a single entry. Don't know what the
> proper way to handle
> > this is.
>
> one way i think
On Sun, Oct 01, 2006 at 12:57:01PM -0500, Myrddin Emrys wrote:
> I believe you still need the ;, even when doing multiline. So that would be:
>
> begin;
> foo;
> end
shouldn't be the case. you don't need them in scripts, so you shouldn't
need them in multiline editing.
> or somesuch. I have not
On Sun, Oct 01, 2006 at 06:12:10PM +0200, Axel Liljencrantz wrote:
> * The current history file format can't support multiline commands
> stored as a single entry. Don't know what the proper way to handle
> this is.
one way i think would be to treat:
begin
foo
end
and
begin; foo; end
as e
I've finally gotten around to taking a first stab at
multiline editing. There is a patch in the darcs tree
that enables this.
Features:
* Single-line editing works as before. There should be
no missing features.
* When the return key follows directly after a
backslash, or when the commands on th
27 matches
Mail list logo
