Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Comments in ZLE
- X-seq: zsh-users 13847
- From: Frank Terbeck <ft@xxxxxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: Comments in ZLE
- Date: Sat, 14 Feb 2009 11:02:27 +0100
- In-reply-to: <20090214092857.GA6292@zoidberg>
- Mail-followup-to: zsh-users@xxxxxxxxxx
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <1234561091.502.ezmlm@xxxxxxxxxx> <20090213215839.GB8108@kyag> <20090213220137.GE4167@xxxxxxxxxxxxxxx> <20090214092857.GA6292@zoidberg>
kba <unixprog@xxxxxxxxxxxxxx>:
> On Fri, Feb 13, 2009 at 11:01:37PM +0100, Frank Terbeck wrote:
> > Frank Jeschke <jes@xxxxxxxxx>:
[...]
> > > sss@kyag:[~]$ #vim /tmp/foo
> > > zsh: command not found: #vim
[...]
> >
> > % man zshoptions | less -p INTERACTIVE_COM
>
> I shared Frank's confusion until I recently stumbled over the
> INTERACTIVE_COM option by accident. Is there a specific reason why this
It's actually INTERACTIVE_COMMENTS. I was too lazy to type it out.
Less's -p option just wants a pattern to search for, so that was
enough. :-)
> is off by default? To avoid clashes with commands that start with '#'?
Well, I'd guess it's been done to let people use the hash char without
needing to quote it. After all, who really uses comments in
interactive mode? (yeah, I know some people do. But they can just use
said option.)
> Can '#' be used to do history expansion like '!' or something like this?
Not that I would know, why?
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
Messages sorted by:
Reverse Date,
Date,
Thread,
Author