From: Michael Albinus <michael.albinus@gmx.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: 31558@debbugs.gnu.org
Subject: bug#31558: 27.0; `custom-file' settings messed up by Emacs 27
Date: Wed, 23 May 2018 16:50:51 +0200 [thread overview]
Message-ID: <87fu2ih1dg.fsf@gmx.de> (raw)
In-Reply-To: <8f1290c2-ad20-4ba9-809d-154188bae0fb@default> (Drew Adams's message of "Wed, 23 May 2018 07:07:17 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
Hi Drew,
>> Maybe you put at the beginning of your custom file
>> (or (locate-library "tramp") (provide 'tramp))
>
> Yes, I guess that would work and is better than nothing,
> but it seems wrong to tell Emacs that something has
> been provided that has not. ;-)
>
> Worse than style or ugliness, though, is that there
> might be code here or there that tests
> (featurep 'tramp) and acts accordingly. That code
> surely will be led astray by such a hack.
We're spaeking about Emacs < 22. How many such Emacsen are in use today,
which also use packages checking for Tramp?
> Seems like there should be a way for Tramp and
> Customize to collaborate to produce a conditional
> sexp that does not require tramp unconditionally.
> E.g., one that tests (at time of evaluating
> `custom-set-variables') whether Tramp is even
> included in the Emacs version.
>
> Or maybe somehow just use a soft-require - the
> equivalent of (require 'tramp nil t)? Would that
> work for Tramp, if it were possible for
> `custom-set-variables'?
>
> Seems like something is missing from Emacs for
> such cases. A library wants to ensure that it is
> loaded before evaluating a sexp that sets one of
> its user options. But if loading the library is
> impossible then setting the variable is benign,
> so a soft-require is all that is really needed.
If there were such a possibility I would consider it. But it must
already exist for Emacsen < 22; I doubt we will change them if it's not
possible yet.
And given the low likelihood plus the existing workaround, I believe it
is not worth to spend time for this. Sorry.
Best regards, Michael.
next prev parent reply other threads:[~2018-05-23 14:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 19:04 bug#31558: 27.0; `custom-file' settings messed up by Emacs 27 Drew Adams
2018-05-23 9:07 ` Michael Albinus
2018-05-23 14:07 ` Drew Adams
2018-05-23 14:50 ` Michael Albinus [this message]
2018-05-23 15:47 ` Drew Adams
2018-05-23 18:05 ` Michael Albinus
2018-05-23 18:15 ` Drew Adams
2018-05-23 18:22 ` Michael Albinus
2018-05-23 19:17 ` Drew Adams
2018-05-24 12:43 ` Michael Albinus
2018-05-24 13:47 ` Drew Adams
2018-05-24 13:56 ` Michael Albinus
2018-05-24 14:44 ` Drew Adams
2018-05-24 14:59 ` Michael Albinus
2018-05-24 15:03 ` Drew Adams
2018-05-29 8:11 ` 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=87fu2ih1dg.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=31558@debbugs.gnu.org \
--cc=drew.adams@oracle.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).