From: Byron Rakitzis <byron>
To: rc
Subject: stuff
Date: Fri, 28 Jun 1991 13:07:41 -0500 [thread overview]
Message-ID: <19910628180741.AyWwm8ELkbnwyDikjBsCXOjTHeOqtzda3bNe84kK_2w@z> (raw)
Ok, let me try to address some of the issues that have come up:
1) backquote will change. I'm working on the code right now. It will work like John
"intuitively" expects it to.
2) I think home directory abbreviations are useless. On the system I administer here,
I keep a directory called /u, with soft links in /u pointing to the real home directory
of a user. e.g.,
; ls -l /u/byron
lrwxrwxrwx 1 root 8 Apr 16 11:53 /u/byron -> /a/byron
The advantage of this is that it is not shell-specific; you can ALWAYS refer to /u/byron/foo
and know that it will work.
Finally, I always make the assignment
h=$home
in my rcrc, so I talk about files like $h/lib/sun4/regexp.o, etc. It's not that many
more characters to type (1 more!), after all. Paul Haahr taught me this trick.
3) A general aside: I knew I was opening a can of worms when I added support for GNU
readline. This position may sound incongruous to you, but I REALLY don't want to be
in the business of supporting rc+readline. My ultimate goal is to write a mux-like
xterm so that I can put all of my command editing into the window system, where it
should be. (score 80 on the Pike-o-meter for Byron!)
Let me say that I am distressed; I don't know how to reconcile my desire for a small
shell with users' desire to use readline. Modifying readline to accept $home or $h
instead of ~ sounds like a good idea, but the LAST thing I want to do is create
a set of rc-specific readline sources.
next reply other threads:[~1991-06-28 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-06-28 18:07 Byron Rakitzis [this message]
[not found] <91Jun28.130752cdt.22542@archone.tamu.edu>
1991-06-29 1:10 ` stuff John Mackin
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=19910628180741.AyWwm8ELkbnwyDikjBsCXOjTHeOqtzda3bNe84kK_2w@z \
--to=rc@hawkwind.utcs.toronto.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.
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).