unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "42323@debbugs.gnu.org" <42323@debbugs.gnu.org>
Subject: bug#42323: [External] : Re: bug#42323: 26.3; Doc string of `seq-map'
Date: Sat, 25 Sep 2021 09:28:12 -0700	[thread overview]
Message-ID: <CADwFkmkMiUMCt-jGPvOLdoittvwLNTmxSBEYiUztrkiLjh21TQ@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB54887D65E1281046F6DD6788F3A59@SJ0PR10MB5488.namprd10.prod.outlook.com>

Drew Adams <drew.adams@oracle.com> writes:

> I don't see how what you show fixes the bug in any
> sense at all.  If the bug can't be fixed now, or no
> one has the energy or motivation to fix it now, that
> doesn't change the fact that the bug exists.
>
> It's not fixed, IMO.  Your options, as I see it, are
> (1) close as "won't fix" or (2) leave it open, in
> hopes that someone, at some time, will find the will
> and a way to fix it, and will do so.
>
> My preference is almost always for #2.  Closing bugs
> just to close bugs doesn't improve anything (IMO).
> But it's your call, not mine.  I just don't agree
> that the bug is fixed (based on what you showed), at
> all.

We can have thousands of bug reports about issues that are basically
there because that what the help screen fundamentally looks like and how
it works.

Or we can have a small number of bug reports that concretely proposes
how to improve the things that cause problems in the first place.

I prefer the latter, and therefore I prefer this bug report closed.

In this case, IMO some kind of folding or sections is what is needed.
Or there is some other general feature that we need.  IOW, this needs a
general solution, not N bug reports about all cases where the lack of
such a general solution cause issues.





      parent reply	other threads:[~2021-09-25 16:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 16:01 bug#42323: 26.3; Doc string of `seq-map' Drew Adams
2020-12-09 13:41 ` Lars Ingebrigtsen
2020-12-09 16:11   ` Michael Heerdegen
2020-12-09 16:44     ` Lars Ingebrigtsen
2020-12-09 19:24       ` Michael Heerdegen
2020-12-09 20:00         ` Drew Adams
2020-12-09 20:19         ` Lars Ingebrigtsen
2021-09-25 15:25   ` Stefan Kangas
2021-09-25 16:10     ` bug#42323: [External] : " Drew Adams
2021-09-25 16:21       ` Eli Zaretskii
2021-09-25 16:43         ` Stefan Kangas
2021-09-25 16:28       ` Stefan Kangas [this message]

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=CADwFkmkMiUMCt-jGPvOLdoittvwLNTmxSBEYiUztrkiLjh21TQ@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=42323@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.org \
    /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).