From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: wyuenho@gmail.com, 63300@debbugs.gnu.org
Subject: bug#63300: 29.0.90; Tramp keeps customizing variables on every connection
Date: Tue, 06 Jun 2023 15:04:09 +0300 [thread overview]
Message-ID: <83pm683ih2.fsf@gnu.org> (raw)
In-Reply-To: <873534rfg8.fsf@gmx.de> (message from Michael Albinus on Tue, 06 Jun 2023 13:35:35 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Jimmy Wong <wyuenho@gmail.com>, 63300@debbugs.gnu.org
> Date: Tue, 06 Jun 2023 13:35:35 +0200
>
> > I believe my proposal to make Tramp use variables that are initialized
> > from the user options should solve all of this. Let's wait for
> > Michael to chime in on that.
>
> By this, a user couldn't change the user options later on, after Tramp
> is initilized. And it isn't only Tramp, other packages use
> connection-local variables as well.
There are many options that behave like that. It's nothing new.
> See my other message for a proposal.
If it works, I don't mind, although the solution looks more
complicated (thus more risky during a pretest).
In general, Lisp programs should not modify values of user options,
that is only for the user.
next prev parent reply other threads:[~2023-06-06 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 10:42 bug#63300: 29.0.90; Tramp keeps customizing variables on every connection Jimmy Yuen Ho Wong
2023-06-04 8:59 ` Michael Albinus
2023-06-04 11:30 ` Jimmy Wong
2023-06-04 11:42 ` Michael Albinus
2023-06-04 11:44 ` Jimmy Wong
2023-06-04 11:56 ` Michael Albinus
2023-06-04 11:59 ` Jimmy Wong
2023-06-04 12:05 ` Michael Albinus
2023-06-04 12:16 ` Jimmy Wong
2023-06-04 12:21 ` Michael Albinus
2023-06-04 12:22 ` Jimmy Wong
2023-06-04 16:55 ` Jimmy Wong
2023-06-04 17:24 ` Eli Zaretskii
2023-06-06 11:35 ` Michael Albinus
2023-06-06 12:04 ` Eli Zaretskii [this message]
2023-06-08 8:08 ` Michael Albinus
2023-06-06 11:46 ` Michael Albinus
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=83pm683ih2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63300@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=wyuenho@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).