From: Jean Louis <bugs@gnu.support>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Setting up Theme opening Tramp... I don't get it
Date: Tue, 4 Oct 2022 13:28:18 +0300 [thread overview]
Message-ID: <YzwKwqWaRmJdCzSm@protected.localdomain> (raw)
In-Reply-To: <jwvfsgac1tg.fsf-monnier+emacs@gnu.org>
* Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2022-09-29 06:21]:
> Jean Louis [2022-09-28 21:47:39] wrote:
> > I really don't understand how setting up custom theme requires
> > Tramp. But that is what is happening, setting up custom theme is
> > taking so much longer as it for some reason wants Tramp to establish
> > those connections in backround.
>
> Oh... *those* connections!
>
>
> Stefan
That one above I cannot understand.
It is disturbing that by doing:
1. any Tramp connection
2. Doing other work for hours or days not being disturbed by Tramp
connections or its buffers;
3. That by M-x customize-themes and selecting one of themes I have to
wait longer time until Tramp connections have been maybe
re-established, I cannot know what:
Tramp: Opening connection nil for admin@static using scp...done
Tramp: Opening connection nil for motorolausb using scp...done
Tramp: Opening connection nil for admin@room using scp...done
Those 2 activities, selecting teheme and Tramp connections are not by
common sense related to each other.
Question is why user who needs to change the theme need to wait for
Tramp connections?
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-10-04 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 18:47 Setting up Theme opening Tramp... I don't get it Jean Louis
2022-09-29 3:11 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-04 10:28 ` Jean Louis [this message]
2022-09-29 8:21 ` Felix Dietrich
2022-10-04 10:35 ` Jean Louis
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=YzwKwqWaRmJdCzSm@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).