unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: pieter@vanoostrum.org, 39436@debbugs.gnu.org
Subject: bug#39436: closed (Re: bug#39436: 27.0.60; Documentaion error for package-menu-hide-package)
Date: Sat, 15 Feb 2020 10:25:03 +0200	[thread overview]
Message-ID: <83d0agntpc.fsf@gnu.org> (raw)
In-Reply-To: <87tv3z5vdg.fsf@marxist.se> (message from Stefan Kangas on Sun, 09 Feb 2020 22:00:27 +0100)

> From: Stefan Kangas <stefan@marxist.se>
> Cc: Pieter van Oostrum <pieter@vanoostrum.org>,  39436@debbugs.gnu.org
> Date: Sun, 09 Feb 2020 22:00:27 +0100
> 
> help-debbugs@gnu.org (GNU bug Tracking System) writes:
> 
> >> (although "permanently" sounds quite strong to me.)
> >
> > I've removed "Permanently" and made the description more detailed.
> 
> Thanks.  But in the new text, there seems to be no indication that the
> hidden status is saved for future sessions.
> 
> I'm not sure how to best describe that, if we feel that "permanently"
> is not clear enough.  Maybe we could say something along the lines of
> "for all future sessions" or somesuch.  It's probably also a good idea
> to mention the variable package-hidden-regexps.
> 
> WDYT?

Feel free to make such a change, although I don't particularly see why
we need to emphasize the "future sessions" part here.  We don't
actually say anywhere anything to the contrary, and there are no other
commands that hide stuff only temporarily, do we?





  reply	other threads:[~2020-02-15  8:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 15:10 bug#39436: 27.0.60; Documentaion error for package-menu-hide-package Pieter van Oostrum
2020-02-08  9:41 ` Eli Zaretskii
2020-02-08 13:58   ` Pieter van Oostrum
2020-02-08 14:32     ` Eli Zaretskii
2020-02-09 16:08       ` Pieter van Oostrum
2020-02-09 16:50         ` Eli Zaretskii
2020-02-09 20:50           ` Stefan Kangas
2020-02-15  8:16             ` Eli Zaretskii
2020-02-09 16:52         ` Pieter van Oostrum
2020-02-09 17:32           ` Eli Zaretskii
2020-02-09 19:44             ` Pieter van Oostrum
2020-02-09 20:28               ` Pieter van Oostrum
2020-02-09 20:36                 ` Stefan Kangas
2020-02-09 20:30               ` Stefan Kangas
     [not found] ` <handler.39436.D39436.158115493214005.notifdone@debbugs.gnu.org>
2020-02-09 21:00   ` bug#39436: closed (Re: bug#39436: 27.0.60; Documentaion error for package-menu-hide-package) Stefan Kangas
2020-02-15  8:25     ` Eli Zaretskii [this message]
2020-02-15 10:31       ` Pieter van Oostrum
2020-03-11  2:07       ` Stefan Kangas
2020-03-11  7:36         ` Pieter van Oostrum
2020-03-11 20:37           ` Stefan Kangas
2020-03-11 22:10             ` Pieter van Oostrum
2020-03-14  9:05               ` Stefan Kangas

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=83d0agntpc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39436@debbugs.gnu.org \
    --cc=pieter@vanoostrum.org \
    --cc=stefan@marxist.se \
    /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).