unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 66150@debbugs.gnu.org
Cc: Michael Albinus <michael.albinus@gmx.de>
Subject: bug#66150: 30.0.50; Duplicate :tag in remote-file-name-inhibit-cache
Date: Fri, 22 Sep 2023 12:01:21 +0200	[thread overview]
Message-ID: <875y42msr2.fsf@epfl.ch> (raw)
In-Reply-To: <87wmwimto3.fsf@epfl.ch> (Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors's message of "Fri, 22 Sep 2023 11:41:32 +0200")

Basil L. Contovounesios [2023-09-22 11:41 +0200] wrote:

> Building master, I see the following warning:
>
>   In toplevel form:
>   files.el:1327:12: Warning: in defcustom for ‘remote-file-name-inhibit-cache’:
>   duplicated :tag string in ‘choice’: "Do not use file name cache"
>
> Is the following patch acceptable?
>
> It tries to improve on the following points:
> - Avoid too much negation
> - Fix then/than typo
> - Avoid mid-sentence %v :format since it extends to eol

[...]

> If it's acceptable, does it belong on master or emacs-29?

Actually, shell-highlight-undef-remote-file-name-inhibit-cache exhibits
the same issues, and that was added in 29.1, so perhaps any fix should
go to emacs-29?

Thanks,
-- 
Basil





  parent reply	other threads:[~2023-09-22 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22  9:41 bug#66150: 30.0.50; Duplicate :tag in remote-file-name-inhibit-cache Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 10:01 ` Michael Albinus
2023-09-22 11:24   ` Stefan Kangas
2023-09-22 10:01 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-22 11:37 ` Eli Zaretskii
2023-09-22 13:19   ` Basil L. Contovounesios 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=875y42msr2.fsf@epfl.ch \
    --to=bug-gnu-emacs@gnu.org \
    --cc=66150@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --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).