unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 75306@debbugs.gnu.org
Subject: bug#75306: 31.0.50; Make `small-temporary-file-directory` variable obsolete
Date: Fri, 3 Jan 2025 02:26:29 -0600	[thread overview]
Message-ID: <CADwFkmmgbdNesFfQXkF9V=QtC6CSeqi1CVnP_jGzf-2c6QaCEw@mail.gmail.com> (raw)
In-Reply-To: <87cyh4bfv0.fsf@gmx.de>

Michael Albinus <michael.albinus@gmx.de> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
> Hi Stefan,
>
>> I think the variable doesn't make much sense these days, and should be
>> made obsolete.  Note that it is barely used in Emacs and third-party
>> packages.
>>
>> However, Tramp recently started using the variable as a place to create
>> OpenSSH Unix domain sockets.  May I suggest that Tramp uses some other
>> variable for this purpose, perhaps a Tramp specific one?
>
> Is there a reason that it must be changed? What are the advantages? Does
> it hurt to keep the user option?

It doesn't hurt to keep it.  The advantage is that we get rid of a
redundant variable.

> And in the Tramp case, you break an existing interface. Users have been
> instructed to change the value of small-temporary-file-directory when
> needed. See (info "(tramp) Frequently Asked Questions"), which documents
> a user problem reported on the <tramp-devel@gnu.org> ML.

Thanks.  Would something like this work?

(define-obsolete-variable-alias 'small-temporary-file-directory
  'temporary-file-directory "31.1")





  reply	other threads:[~2025-01-03  8:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03  3:23 bug#75306: 31.0.50; Make `small-temporary-file-directory` variable obsolete Stefan Kangas
2025-01-03  5:56 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-03  8:26   ` Stefan Kangas [this message]
2025-01-03  8:49     ` Eli Zaretskii
2025-01-03  8:39   ` Eli Zaretskii
2025-01-03  9:15     ` Stefan Kangas
2025-01-03 11:46       ` Eli Zaretskii
2025-01-04  9:54   ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04  9:54   ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <87ttaezyyp.fsf@>
2025-01-04 11:26     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04 22:16       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04 22:16       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]       ` <6779b38c.050a0220.be2ea.a6e0SMTPIN_ADDED_BROKEN@mx.google.com>
2025-01-05  5:30         ` Stefan Kangas
     [not found]       ` <8734hyw7g4.fsf@>
2025-01-05  8:18         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='CADwFkmmgbdNesFfQXkF9V=QtC6CSeqi1CVnP_jGzf-2c6QaCEw@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=75306@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).