From: "David J. Fiander" <davidf@golem.uucp>
To: Bob Gibson <rjg@sco.COM>
Cc: The rc Mailing List <rc@hawkwind.utcs.toronto.edu>
Subject: Re: recent -s patch
Date: Mon, 29 Jun 1992 19:19:22 -0400 [thread overview]
Message-ID: <9206291919.aa27683@golem.UUCP> (raw)
In-Reply-To: Your message of "Sun, 28 Jun 92 21:36:55 EDT." <9206282136.aa02955@imp.scocan.sco.COM>
>From: Bob Gibson <rjg@sco.com>
>| Hey, can anyone on the list tell us
>| all if they have any reason at all for wanting -s? Inquiring minds
>| want to know. So far, we have Rich's reason, which is that -s is
>| passed to the invoked shell by `the OSF/1 script command'. Any
>| other takers?
>
>My editor, jove, starts up subshells with the -s option, and obviously
>fails to do so if the shell doesn't support it. In this case, the
>correct thing to do would be to fix jove to make this configurable.
The reason that jove does this is because is starts the shell
with either its command line arguments or the file names
associated with its buffers as arguments to the shell. That
is, is says
$SHELL -s file1 file2 file3
This way you can easily refer to the files you are editting in
your subshell.
It would be nice if this feature was documented, though.
- David
next prev parent reply other threads:[~1992-06-29 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-06-29 1:36 Bob Gibson
1992-06-29 23:19 ` David J. Fiander [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-06-26 4:11 Scott Schwartz
1992-06-28 19:47 ` John Mackin
1992-06-28 20:34 ` Scott Schwartz
1992-06-28 21:01 ` 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=9206291919.aa27683@golem.UUCP \
--to=davidf@golem.uucp \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=rjg@sco.COM \
/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).