From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Off Topic
Date: Thu, 24 May 2018 20:07:31 +0300 [thread overview]
Message-ID: <834lixasoc.fsf@gnu.org> (raw)
In-Reply-To: <87tvqxrrhr.fsf@gmail.com> (message from Robert Pluim on Thu, 24 May 2018 17:41:04 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 24 May 2018 17:41:04 +0200
>
> > I'm all for more documentation, but in this case what would you add to
> > the doc string that already is very long and very detailed?
>
> I meant documentation of its existence, something like:
I very much doubt this will increase the package's visibility, but
saying that certainly doesn't hurt.
Thanks.
next prev parent reply other threads:[~2018-05-24 17:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 11:18 bug#31544: Emacs 26.1 rc-1 Texinfo View fails to italicize all 6 lines in paragraph Van L
2018-05-21 16:23 ` Eli Zaretskii
2018-05-21 23:45 ` Van L
2018-05-22 2:13 ` Richard Stallman
2018-05-22 2:40 ` Van L
2018-05-22 4:32 ` Eli Zaretskii
2018-05-22 6:58 ` Off Topic (was: bug#31544) Van L
2018-05-23 3:24 ` Richard Stallman
2018-05-23 3:44 ` Van L
2018-05-23 11:06 ` Noam Postavsky
2018-05-24 2:48 ` Richard Stallman
2018-05-24 9:03 ` Off Topic Robert Pluim
2018-05-24 15:20 ` Eli Zaretskii
2018-05-24 15:41 ` Robert Pluim
2018-05-24 17:07 ` Eli Zaretskii [this message]
2018-05-25 2:59 ` Richard Stallman
2018-05-24 16:35 ` Off Topic (was: bug#31544) Alan Mackenzie
2018-05-24 16:53 ` Yuri Khan
2018-05-24 19:57 ` Alan Mackenzie
2018-05-24 20:24 ` Noam Postavsky
2018-05-24 20:36 ` Off Topic Stefan Monnier
2018-05-25 3:01 ` Off Topic (was: bug#31544) Richard Stallman
2018-05-25 2:59 ` Richard Stallman
2018-05-24 17:01 ` Eli Zaretskii
2018-05-28 22:42 ` bug#31544: Emacs 26.1 rc-1 Texinfo View fails to italicize all 6 lines in paragraph Noam Postavsky
2022-01-23 13:57 ` bug#31544: texinfo-mode fails to consistently fontify multiline @i{italic text} Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834lixasoc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.