From: Jimmy Wong <wyuenho@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 63300@debbugs.gnu.org
Subject: bug#63300: 29.0.90; Tramp keeps customizing variables on every connection
Date: Sun, 4 Jun 2023 13:22:35 +0100 [thread overview]
Message-ID: <af9da4b6-9a75-4d40-9b6b-9bffc986399e@Spark> (raw)
In-Reply-To: <87o7lvquy2.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
I’ll file a separate bug. You can close this one. Thanks.
On 4 Jun 2023 at 1:21 PM +0100, Michael Albinus <michael.albinus@gmx.de>, wrote:
> Jimmy Wong <wyuenho@gmail.com> writes:
>
> Hi,
>
> > Well, yes, I consider this a poorly considered “feature”, or arguably
> > a bug, for exactly the reason you said, they are local to connections
> > and machines, and thus highly variable.
>
> Not really. They exist for the reason that a user can override the
> default values offered by Tramp. This I would call a user option.
>
> Tramp has a lot of further host specific data, which are all kept in
> variables.
>
> > We can probably argue whether this is a bug in tramp or a bug in
> > customize-save-variable tho (why on earth does the act of saving a
> > single variable value saves all customized values if a custom file
> > exists?)
>
> I agree with the latter.
>
> Best regards, Michael.
[-- Attachment #2: Type: text/html, Size: 1457 bytes --]
next prev parent reply other threads:[~2023-06-04 12:22 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 [this message]
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
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=af9da4b6-9a75-4d40-9b6b-9bffc986399e@Spark \
--to=wyuenho@gmail.com \
--cc=63300@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).