unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jimmy Wong <wyuenho@gmail.com>
Cc: michael.albinus@gmx.de, 63300@debbugs.gnu.org
Subject: bug#63300: 29.0.90; Tramp keeps customizing variables on every connection
Date: Sun, 04 Jun 2023 20:24:06 +0300	[thread overview]
Message-ID: <8335375efd.fsf@gnu.org> (raw)
In-Reply-To: <3aba5090-3ed7-4a2b-b65c-872880e2bf76@Spark> (message from Jimmy Wong on Sun, 4 Jun 2023 17:55:42 +0100)

> Cc: 63300@debbugs.gnu.org
> Date: Sun, 4 Jun 2023 17:55:42 +0100
> From: Jimmy Wong <wyuenho@gmail.com>
> 
> Actually, I take it back. customize-save-variable only saves variables that have the saved-value
> symbol property set. This property is normally set by customize when it is saved to the custom file.
> Something in Tramp is setting this property without saving the variable values to the custom file or
> going through customize. In fact, you can see it via M-x customize-option
> connection-local-criteria-alist. The value will be shown as SAVED.

Maybe Tramp uses setopt or something to change the values of these
options?  Michael?

> Both of this behavior violate what is documented in the docstring and
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Standard-Properties.html.
> 
> If you must, enable-conneciton-local-variables should be respected, and if you must, set the
> theme-value property on these connection-local variables instead of saved-value so custom-save-all
> will not save them.

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.





  reply	other threads:[~2023-06-04 17:24 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 [this message]
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=8335375efd.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).