From: "KARR, DAVID" <dk068x@att.com>
To: tpeplt <tpeplt@gmail.com>
Cc: "Help-gnu-emacs@gnu.org" <Help-gnu-emacs@gnu.org>
Subject: RE: In eshell, how to translate aliases that "eval" output from scripts
Date: Sun, 11 Aug 2024 06:53:03 +0000 [thread overview]
Message-ID: <DM3PR02MB1025646DCE1BCDB33DAAEE9DA9D842@DM3PR02MB10256.namprd02.prod.outlook.com> (raw)
In-Reply-To: <87h6bsqak3.fsf@gmail.com>
Yes, I saw the part about defining aliases. That is the trivial part of this question.
From: tpeplt <tpeplt@gmail.com>
Sent: Saturday, August 10, 2024 3:26 PM
To: KARR, DAVID <dk068x@att.com>
Cc: Help-gnu-emacs@gnu.org
Subject: Re: In eshell, how to translate aliases that "eval" output from scripts
"KARR, DAVID" <dk068x@ att. com> writes: > In my bash config, I have aliases whose value is like ". scriptname". > These execute "scriptname", which is in the path, the output of which > are "export" and other shell commands. This
"KARR, DAVID" <dk068x@att.com<mailto:dk068x@att.com>> writes:
> In my bash config, I have aliases whose value is like ". scriptname".
> These execute "scriptname", which is in the path, the output of which
> are "export" and other shell commands. This is a way of having a
> shell command implicitly set environment variables that are used by
> later command invocations. What's the proper way to translate this to
> eshell?
See:
(info "(eshell) Built-ins")
and
(info "(eshell) Aliases")
--
The lyf so short, the craft so long to lerne.
- Geoffrey Chaucer, The Parliament of Birds.
next prev parent reply other threads:[~2024-08-11 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 21:16 In eshell, how to translate aliases that "eval" output from scripts KARR, DAVID
2024-08-10 22:26 ` tpeplt
2024-08-11 6:53 ` KARR, DAVID [this message]
2024-08-11 11:31 ` Joel Reicher
2024-08-11 23:48 ` Joel Reicher
2024-08-14 2:15 ` James Thomas
2024-08-14 11:00 ` Joel Reicher
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=DM3PR02MB1025646DCE1BCDB33DAAEE9DA9D842@DM3PR02MB10256.namprd02.prod.outlook.com \
--to=dk068x@att.com \
--cc=Help-gnu-emacs@gnu.org \
--cc=tpeplt@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.