From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: require basic stuff from specific packages
Date: Tue, 05 Jul 2016 02:44:57 +0200 [thread overview]
Message-ID: <86y45glxpy.fsf@student.uu.se> (raw)
In-Reply-To: m38txhu7mr.fsf@gnus.org
Lars Magne Ingebrigtsen <lmi@gnus.org> writes:
>> (erc-trim-string string) ; here
>
> Use `string-trim' instead.
>
> `erc-trim-string' demonstrates why having
> compat functions strewn around various packages
> is unhelpful for users trying to navigate the
> Emacs code base.
Yes, `string-trim' in in subr-x does it!
How are you supposed to find it tho?
Now I asked here. It isn't a bad way. But if we
exclude that as well as greping the web, I mean.
Because what I did was using `apropos'.
The reason it found the ERC stuff and not the
subr-x is because I had ERC loaded as my
IRC client, and subr-x wasn't even loaded!
Here is another example:
(defun buffer-names ()
"Get a list of all `buffer-name's."
(mapcar #'buffer-name (buffer-list)) )
If I write two or more packs that both/all use
it, where do I put it? I don't want to put the
same thing in every one. But I don't want to
require it either because the packs are
one-file and I don't want to have the user have
to install yet another package to use them.
Especially since it would amount to countless
such packages... Perhaps I should put all into
one helper-pack and have just one (require
'mannys-utils) in all the rest!
--
underground experts united .... http://user.it.uu.se/~embe8573
Emacs Gnus Blogomatic ......... http://user.it.uu.se/~embe8573/blogomatic
- so far: 56 Blogomatic articles -
next prev parent reply other threads:[~2016-07-05 0:44 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 [this message]
2016-07-13 1:26 ` Howard Melman
2016-07-13 1:58 ` Drew Adams
[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=86y45glxpy.fsf@student.uu.se \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@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.
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).