From: Matt Liggett <mliggett@seven.ucs.indiana.edu>
To: zsh-workers@math.gatech.edu
Subject: couple of zsh features
Date: Thu, 07 Dec 1995 11:31:22 -0500 [thread overview]
Message-ID: <199512071631.LAA01231@seven.ucs.indiana.edu> (raw)
Fellow zsh hackers,
I was talking to a friend about shells the other night when the
discussion of a couple of neat features came up. There are a couple
of features which we both thought could be very valuable and I'd like
to know if anyone is working or has worked on them so I don't
re-invent the wheel if I decide to delve into the source.
1) Right-hand command prompting.
I know about RPS*, but how about a right-hand command prompt like
so:
213 19:22 <seven:~
213 19:22 l<seven:~
213 19:22 ls<seven:~
213 19:22 ls <seven:~
213 19:22 ls -<seven:~
213 19:22 ls -l<seven:~
This shows how the line would progress as each command was typed.
The stuff on the left is what I tend to keep in my prompt (history
number and time). I think this sort of "right justifying" could be a
good visual clue for some people and help them set commands off from
output.
2) `oops'
Any of you ever used Infocom games or other interactive fiction?
The construct is simple:
> get sord
?- What's a sord?
> oops sword
Taken.
In this example, it doesn't save you much work, but it can many other
times. What oops does is takes the first word that failed to parse
correctly in the previous line and replaces it with its argument.
Maybe some kind of compctl-based matching could be used to determine
which word in the previous command was a likely mismatch.
Thoughts?
--
http://seven.ucs.indiana.edu/~mliggett ||| Matt Liggett |
$_="5673089a34120b12c048de12f\n"; /// ||| <mliggett@indiana.edu> |
@j=split//," erthJusanoPlck."; /// ||| '70 Midget '74 Bronco |
s/./$j[hex $&]/ge;print /// ||| '78 Civic 1200 |
next reply other threads:[~1995-12-07 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-07 16:31 Matt Liggett [this message]
[not found] ` <mliggett@seven.ucs.indiana.edu>
1995-12-07 17:29 ` Barton E. Schaefer
1995-12-07 17:59 ` Matt Liggett
1995-12-08 9:07 ` Bas V. de Bakker
1995-12-07 20:22 ` Richard Coleman
1995-12-07 19:02 ` Barton E. Schaefer
1995-12-08 7:20 Sven Wischnowsky
1995-12-16 0:52 Thomas Pierre Schweikle
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=199512071631.LAA01231@seven.ucs.indiana.edu \
--to=mliggett@seven.ucs.indiana.edu \
--cc=mliggett@indiana.edu \
--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).