From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Aidan Gauland <aidalgol@no8wireless.co.nz>
Cc: emacs-diffs@gnu.org, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r112148: Added eshell-tramp module
Date: Thu, 28 Mar 2013 09:16:52 -0400 [thread overview]
Message-ID: <jwv8v57aco0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87hajw6iog.fsf@no8wireless.co.nz> (Aidan Gauland's message of "Thu, 28 Mar 2013 21:18:55 +1300")
>> This said, IIUC just loading eshell-tramp.el will also enable it (tho
>> not "completely"). That's a problem (and yes, this is not a new
>> problem, it's just a problem in most/all eshell modules).
> Yes, if the feature `em-tramp' is loaded but the module is not enabled,
> then it is just taking up memory and doing nothing.
Just taking up memory is not a problem. But IIUC since it defines
eshell/su, it will have an impact on eshell buffers, even if
eshell-tramp-initialize is not called, right?
Stefan
next prev parent reply other threads:[~2013-03-28 13:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1UKcBA-00086f-PW@vcs.savannah.gnu.org>
[not found] ` <jwvip4dfxbh.fsf-monnier+emacs@gnu.org>
[not found] ` <87wqst2vw3.fsf@no8wireless.co.nz>
[not found] ` <jwv8v59dmlj.fsf-monnier+emacs@gnu.org>
2013-03-28 8:18 ` /srv/bzr/emacs/trunk r112148: Added eshell-tramp module Aidan Gauland
2013-03-28 10:19 ` Michael Albinus
2013-03-28 20:00 ` Aidan Gauland
2013-03-28 20:23 ` Eli Zaretskii
2013-03-28 22:02 ` Aidan Gauland
2013-03-29 5:38 ` Eli Zaretskii
2013-03-28 21:01 ` Michael Albinus
2013-03-28 21:52 ` Aidan Gauland
2013-03-29 8:28 ` Michael Albinus
2013-03-28 13:16 ` Stefan Monnier [this message]
2013-03-28 20:03 ` Aidan Gauland
[not found] ` <87wqsrnvsh.fsf@dimension8.tehua.net>
[not found] ` <jwvfvzfdytf.fsf-monnier+emacs@gnu.org>
2013-03-29 0:09 ` [Emacs-diffs] " Aidan Gauland
2013-03-29 20:30 ` Stefan Monnier
2013-03-30 3:14 ` Aidan Gauland
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=jwv8v57aco0.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=aidalgol@no8wireless.co.nz \
--cc=emacs-devel@gnu.org \
--cc=emacs-diffs@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.
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.