unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: rgm@gnu.org, larsi@gnus.org, jonas@bernoul.li,
	p.stephani2@gmail.com, 53316@debbugs.gnu.org
Subject: bug#53316: 28.0.91; Missing Transient manual in Emacs
Date: Wed, 23 Feb 2022 14:45:25 +0200	[thread overview]
Message-ID: <8335k9u4yi.fsf@gnu.org> (raw)
In-Reply-To: <E1nMlP3-0008Bh-J2@fencepost.gnu.org> (message from Richard Stallman on Wed, 23 Feb 2022 01:45:33 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: rgm@gnu.org, larsi@gnus.org, jonas@bernoul.li,
> 	p.stephani2@gmail.com, 53316@debbugs.gnu.org
> Date: Wed, 23 Feb 2022 01:45:33 -0500
> 
>     > Removing its manual is only acceptable to me if we also remove
>     > the package and all its uses.
> 
> Lots of packages don't have manuals.  Indeed, it is undesirable not to
> have the Texinfo manual, but not a disaster.

It is in this case, IMO.  I suggest that you take a quick look at
transient.el and consider whether it is easy to grasp without a decent
manual.  My firm opinion is that it is very hard for the uninitiated.

>   > For future releases, we indeed hope to see the problems of
>   > conversion from Org resolved,
> 
> That would be a very good advance; but because it's difficult and
> because I've seen people neglect the issue before, could you ask
> the people doing this to show me the spec they want to implement?

Jonas explicitly said he is working on this, so I find it hard to
believe that this won't be solved soon enough, worst case in time for
Emacs 29.





  parent reply	other threads:[~2022-02-23 12:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 13:07 bug#53316: 28.0.91; Missing Transient manual in Emacs Philipp Stephani
2022-01-21 11:29 ` Lars Ingebrigtsen
2022-01-25 20:30   ` Jonas Bernoulli
2022-01-25 20:41     ` Philipp Stephani
2022-01-25 21:15       ` Jonas Bernoulli
2022-02-15 16:57         ` Jonas Bernoulli
2022-01-26  9:08     ` Michael Albinus
2022-02-15 16:53   ` Jonas Bernoulli
2022-02-15 19:09     ` Eli Zaretskii
2022-02-15 21:39       ` Jonas Bernoulli
2022-02-16  3:25         ` Eli Zaretskii
2022-02-15 20:17     ` Glenn Morris
2022-02-15 21:46       ` Jonas Bernoulli
2022-02-16 21:09         ` Glenn Morris
2022-02-17  6:23           ` Eli Zaretskii
2022-02-19  4:57             ` Richard Stallman
2022-02-19  8:46               ` Eli Zaretskii
2022-02-21  4:34                 ` Richard Stallman
2022-02-21  5:47                   ` Eli Zaretskii
2022-02-23  6:45                     ` Richard Stallman
2022-02-23 12:18                       ` Jonas Bernoulli
2022-02-25  5:00                         ` Richard Stallman
2022-02-23 12:45                       ` Eli Zaretskii [this message]
2022-02-19  9:27               ` Glenn Morris

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=8335k9u4yi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53316@debbugs.gnu.org \
    --cc=jonas@bernoul.li \
    --cc=larsi@gnus.org \
    --cc=p.stephani2@gmail.com \
    --cc=rgm@gnu.org \
    --cc=rms@gnu.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).