unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: 47287@debbugs.gnu.org
Cc: theo@thornhill.no, dgutov@yandex.ru
Subject: bug#47287: 28.0.50; [PATCH] Add command project-remove-known-project
Date: Thu, 25 Mar 2021 00:03:13 +0000	[thread overview]
Message-ID: <87lfacxfpa.fsf@tcd.ie> (raw)
In-Reply-To: <61faf9a5-266e-2077-71bd-d64564914671@yandex.ru> (Dmitry Gutov's message of "Thu, 25 Mar 2021 01:17:39 +0200")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 23.03.2021 14:50, Theodor Thornhill via Bug reports for GNU Emacs, the Swiss
> army knife of text editors wrote:
>> 
>>> One last nit from me: since you now include the changes to the manual,
>>> this NEWS entry should be marked by "+++" before it, per the note at
>>> the beginning of NEWS.
>> Of course - added. Thanks for patience :)
>
> Thank you for following up.
>
> Installed and closing.

Thanks, this is a useful function I wished for recently.

But Texinfo still had some comments on the patch ;).

  ./maintaining.texi:1821: warning: node `Managing project list file' is
  next for `Switching Projects' in sectioning but not in menu
  ./maintaining.texi:1846: warning: node `Switching Projects' is prev
  for `Managing project list file' in sectioning but not in menu
  ./maintaining.texi:1846: warning: node `Projects' is up for `Managing
  project list file' in sectioning but not in menu
  ./maintaining.texi:1641: node `Projects' lacks menu item for `Managing
  project list file' despite being its Up target

Could you please add a menu entry for the new node?

(There also seem to be some extraneous parentheses around
@code{project-list-file}, a missing space after full stop, and a missing
full stop in the new text.)

Thanks,

-- 
Basil





  reply	other threads:[~2021-03-25  0:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20 23:28 bug#47287: 28.0.50; [PATCH] Add command project-remove-known-project Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21  0:27 ` Dmitry Gutov
2021-03-21  6:33   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 11:42     ` Dmitry Gutov
2021-03-21  6:17 ` Eli Zaretskii
2021-03-21  6:38   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 12:12     ` Dmitry Gutov
2021-03-21 12:15       ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 23:21       ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 23:54         ` Dmitry Gutov
2021-03-22  7:48           ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-22 11:52             ` Dmitry Gutov
2021-03-22 12:29               ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-23 11:37             ` Eli Zaretskii
2021-03-23 12:30               ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-23 12:43                 ` Eli Zaretskii
2021-03-23 12:50                   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-24 23:17                     ` Dmitry Gutov
2021-03-25  0:03                       ` Basil L. Contovounesios [this message]
2021-03-25  1:04                         ` Dmitry Gutov
2021-03-25  6:15                           ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-25  7:29                             ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-21 13:24                               ` Dmitry Gutov
2021-09-21 18:36                                 ` Theodor Thornhill 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=87lfacxfpa.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=47287@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=theo@thornhill.no \
    /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).