From: Drew Adams <drew.adams@oracle.com>
To: Howard Melman <hmelman@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: require basic stuff from specific packages
Date: Tue, 12 Jul 2016 18:58:02 -0700 (PDT) [thread overview]
Message-ID: <8ae64b0e-1ff9-46ed-a9fa-38790f9ffa61@default> (raw)
In-Reply-To: <lyshveba5b.fsf@Lumet.home>
> > Yes, `string-trim' in in subr-x does it!
> > How are you supposed to find it tho?
>
> In this case it's particularly egregious because sub-x.el
> isn't documented in the lisp manual or in any other manual.
>
> Perhaps a page in the lisp manual describing these 11
> functions, saying these are potentially useful, would mean
> that someone would find them, use them and then we'd be able
> to deem them useful.
Neither the Emacs manual nor the Elisp manual documents all
commands, let alone all functions, that are useful. (And
libraries are typically not mentioned as such.)
It's always a judgment call what to put in a manual, but there
will always be tons of functions and variables that cannot
(and in most cases should not) be documented in the manuals.
This one is essentially a utility function. If it were
autoloaded then it would be relatively easy to discover using
completion: `C-h f string TAB'. (And if you have a better
completion system you can also use `C-h f trim TAB'.)
If you think that a particular thing (e.g. function) should
be documented in the manual, the way to get your voice heard
is to file a bug report (aka enhancement request):
`M-x report-emacs-bug'. Likewise, if you would like to suggest
that such a function be autoloaded.
next prev parent reply other threads:[~2016-07-13 1:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 23:13 require basic stuff from specific packages Emanuel Berg
2016-07-04 8:10 ` Stefan Monnier
2016-07-04 8:31 ` Lars Magne Ingebrigtsen
2016-07-05 0:44 ` Emanuel Berg
2016-07-13 1:26 ` Howard Melman
2016-07-13 1:58 ` Drew Adams [this message]
[not found] ` <mailman.1251.1468375187.26859.help-gnu-emacs@gnu.org>
2016-07-13 2:11 ` Emanuel Berg
[not found] ` <mailman.1248.1468373420.26859.help-gnu-emacs@gnu.org>
2016-07-13 2:06 ` Emanuel Berg
2016-07-13 13:31 ` Howard Melman
2016-07-13 14:10 ` Drew Adams
[not found] ` <mailman.1273.1468416740.26859.help-gnu-emacs@gnu.org>
2016-07-13 13:40 ` Emanuel Berg
2016-07-13 15:13 ` Drew Adams
[not found] ` <mailman.1301.1468422827.26859.help-gnu-emacs@gnu.org>
2016-07-13 16:07 ` Emanuel Berg
2016-07-13 16:16 ` Kaushal Modi
2016-07-13 16:19 ` Kaushal Modi
2016-07-13 16:41 ` Drew Adams
2016-07-13 16:25 ` Drew Adams
[not found] ` <mailman.1322.1468427133.26859.help-gnu-emacs@gnu.org>
2016-07-13 19:24 ` Emanuel Berg
2016-07-14 3:12 ` Howard Melman
[not found] ` <mailman.1377.1468465957.26859.help-gnu-emacs@gnu.org>
2016-07-15 1:49 ` Emanuel Berg
2016-07-16 7:07 ` Emanuel Berg
2016-07-19 20:43 ` EB double-grep function for bash Tomas Nordin
2016-07-14 1:35 ` require basic stuff from specific packages Emanuel Berg
2016-08-09 14:16 ` Udyant Wig
2016-08-10 15:39 ` Emanuel Berg
2016-08-10 15:51 ` Drew Adams
2016-08-10 17:54 ` Udyant Wig
2016-08-10 19:43 ` Emanuel Berg
2016-08-11 5:38 ` Udyant Wig
2016-08-11 14:49 ` Eli Zaretskii
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=8ae64b0e-1ff9-46ed-a9fa-38790f9ffa61@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=hmelman@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.
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).