From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@math.gatech.edu, Andrew Main <zefram@tao.co.uk>,
Quinn Dunkan <quinn@envy.ugcs.caltech.edu>
Subject: Re: ideas, questions, and bugs (?)
Date: Wed, 8 Oct 1997 09:26:17 -0700 [thread overview]
Message-ID: <971008092617.ZM9788@candle.brasslantern.com> (raw)
In-Reply-To: <199710080711.AAA01989@tammananny.tiger>
In-Reply-To: <199710080934.KAA07190@taos.demon.co.uk>
On Oct 8, 10:34am, Andrew Main wrote:
} Subject: Re: ideas, questions, and bugs (?)
}
} >As much as I try, I can't figure out a good way to have zsh execute some
} >command at startup and stay in interactive mode.
}
} Funnily enough, `interactive' implies interaction with the user. If you
} want interaction in a shell script, use vared.
The documentation should probably explain that -s and -i are mutually
exclusive and that -i always wins. Given just what's written down, one
would think that
echo 'echo foo ; exec < /dev/tty' | zsh -si
would "do the right thing".
} >instead of just beeping when the user attempts to scroll the history
} >past the current line, zsh should just predict the user's next command,
} >so you could have a forward 'history' as well.
}
} I'd already considered doing this; history references like "!+1" ought
} to work. Of course, to get commands from future sessions you'll need
} a history file saved on a trfs (temporally reversed filesystem -- the
} media uses positrons instead of electrons).
Something I've been wishing for was a variant of infer-next-history that
would work like this:
If the current command line is either empty or matches "!-1", then search
backwards from "!-2" for another occurrence of the same line, and infer
the event that follows it.
However, at the moment in zsh-3.0.[45], I can't get infer-next-history to
do anything other than beep at me no matter what the current line looks
like nor what's in the history. Is it just me?
} >In zsh 3.0.0, PATH always reflecs path, and vice-versa. In zsh 3.1.2, PATH
} >reflects path only if PATH is set.
}
} This is a feature. Don't unset PATH if you want it to be available.
Um, what feature is this supposed to be providing? And it shouldn't seg
fault in any case.
On Oct 8, 12:11am, Quinn Dunkan wrote:
} My zsh 3.1.2 segfaults when it can't find PATH. This seems like a bug.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next parent reply other threads:[~1997-10-08 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199710080711.AAA01989@tammananny.tiger>
[not found] ` <199710080934.KAA07190@taos.demon.co.uk>
1997-10-08 16:26 ` Bart Schaefer [this message]
[not found] <199710082011.UAA00314@dal-tsa6-26.cyberramp.net>
[not found] ` <m3d8lehl9b.fsf@snoopy.ftlsol.com>
1997-10-09 18:52 ` Stefan Monnier
[not found] <199710080911.KAA06762@taos.demon.co.uk>
1997-10-08 9:47 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=971008092617.ZM9788@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=quinn@envy.ugcs.caltech.edu \
--cc=zefram@tao.co.uk \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).