From: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu>
To: The rc Mailing List <rc@archone.tamu.edu>
Subject: Re: early reaction(s) to rc
Date: Mon, 26 Aug 1991 21:28:14 -0500 [thread overview]
Message-ID: <91Aug26.222817edt.2702@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: john's message of Fri, 23 Aug 91 09:40:03 -0400. <9108232340.26762.rc.bafoj@syd.dit.csiro.au>
[This is part 1 of N parts of stuff; more to come as I digest and
comment on my pile of email.]
John writes:
| This is what I fail to follow; I don't understand why one needs to tell
| whether or not the shell is interactive in order to accomplish the goal
| of making a root prompt be something arbitrary.
Figuring out what the root prompt should be may take a significant
number of (potentially expensive) operations; I'd like to do it only
when necessary, to avoid the performance hit.
In hindsight, setting the root prompt was a bad example of per-shell
startup actions. A much better one for people with windowing systems
is arranging a per-window history, something that is highly useful
(especially for me, as just specifying a global history file seems to
result in all sorts of interesting jumbling up of stuff). For X, one
can almost get there cheaply with a prompt function, but it's not
quite close enough (and going the final step is expensive; you need to
check what your current tty is, which is not something I want to do
for every prompt).
- cks
next prev parent reply other threads:[~1991-08-27 2:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-08-23 1:36 new list subscriber Byron Rakitzis
1991-08-23 13:40 ` early reaction(s) to rc John Mackin
1991-08-27 2:28 ` Chris Siebenmann [this message]
1991-08-23 16:24 Arnold D. Robbins
1991-08-27 2:33 ` Chris Siebenmann
1991-08-23 16:51 DaviD W. Sanderson
1991-08-23 17:07 ` Boyd Roberts
1991-08-23 20:47 Arnold D. Robbins
1991-08-24 0:15 ` John Mackin
1991-08-24 3:48 ` John Mackin
1991-08-27 6:24 Paul Haahr
1991-08-27 7:15 ` Chris Siebenmann
1991-08-27 10:22 ` Boyd Roberts
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=91Aug26.222817edt.2702@hawkwind.utcs.toronto.edu \
--to=cks@hawkwind.utcs.toronto.edu \
--cc=rc@archone.tamu.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).