From: Pawel <mafeusek@gmail.com>
To: GNU emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: tramp. bash aliases
Date: Thu, 01 Apr 2010 20:33:03 +0200 [thread overview]
Message-ID: <m2zl1nauml.fsf@gmail.com> (raw)
In-Reply-To: <756C3B76-6884-43AF-B04E-855DAB15330F@Web.DE> (Peter Dyballa's message of "Thu, 1 Apr 2010 17:02:40 +0200")
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
>
> Do you mean something like ~/.emacs_bash? This file, if it exists, is executed when you
> start a shell in *shell* buffer. (Similarly RC files exist for bash when you have a
> non-login non-interactive bash session...)
No. I mean "alias", for example my_ls='ls -l' that will be configured in
my local ~/.emacs and when I do M-x shell on remote machine, this alias
is able to be invoked on behalf of remote machine. Thus, only one configuration
on local site for many remote hosts.
best regards,
Pawel
next prev parent reply other threads:[~2010-04-01 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 12:23 tramp. bash aliases Pawel p
2010-04-01 15:02 ` Peter Dyballa
2010-04-01 18:33 ` Pawel [this message]
2010-04-01 20:17 ` Peter Dyballa
2010-04-01 20:28 ` Pawel
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2zl1nauml.fsf@gmail.com \
--to=mafeusek@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).