From: dws@cs.wisc.edu (DaviD W. Sanderson)
To: rc@archone.tamu.edu
Subject: opposite of builtin is builtin
Date: Mon, 1 Jul 1991 17:05:20 -0500 [thread overview]
Message-ID: <9107012205.AA11467@margay.cs.wisc.edu> (raw)
Mark-Jason Dominus <mjd@saul.cis.upenn.edu> wrote:
> There is a `builtin' command,
...
> It might be nice to have a similar functionality for non-builtin
> functions,
Byron has suggested in mail to me that he will change "builtin" to
go through the normal process of executing the given command, except
that the normal search for a function of that name will be supressed.
This implies a path search if the given command is not a builtin.
Currently I have this in my .rcrc file to provide a front end function
for the 'ls' command which adds options I like if the output is to the
tty:
eval ( \
fn ls '{' \
'test -t 1 && * = (-FCb $*);' \
`{whatis ls} '$*' \
'}' \
)
If Byron changes builtin as he suggested, I will be able to use this
much more aesthetic function instead:
fn ls {
test -t 1 && * = (-FCb $*)
builtin ls $*
}
DaviD W. Sanderson (dws@cs.wisc.edu)
reply other threads:[~1991-07-01 22:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9107012205.AA11467@margay.cs.wisc.edu \
--to=dws@cs.wisc.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).