From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: "'Help-Gnu-Emacs \(help-gnu-emacs@gnu.org\)'" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : (bounds-of-thing-at-point 'number) ⇒ nil
Date: Sat, 5 Feb 2022 17:27:33 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488A818581ED448E6B4CC0EF32A9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87a6f6f54p.fsf@zoho.eu>
[-- Attachment #1: Type: text/plain, Size: 2572 bytes --]
> >> You got it to work with the alternative
> >> package, thingatpt+?
> >
> > Got what to work? thingatpt+.el isn't an
> > alternative in the sense that it replaces
> > thingatpt.el. It fixes and extends stuff
> > in the latter. It builds on it.
>
> Okay, alternative function then.
I repeat, "Got what to work?"
___
> As for what is `require'd no need to communicate that to
> anyone since it is handled by/in library+'s source ...
I was explaining to you the file-name convention I
use, since you brought up the `+' in the file name.
> > (I've even had a couple libraries with suffix - instead of
> > +, where - means load before the library to be extended, and
> > + means load after it.)
>
> A clever little game in your mind and by all means, but it
> doesn't look good and with the hyphen-minus it looks even
> worse since that is used as our beloved
> lisp-word-separator ...
File-name syntax has nothing to do with Lisp syntax.
That some file name "doesn't look good" to you is,
well, too bad. You're not obliged to like it. ;-)
> And there is no need to communicate any of that,
No. Users can sometimes need to know how and when
to load a library.
> anything should be possible to load at any time
Absolutely not - if the intended behavior is to
be achieved. Load order of libraries matters, in
general. Loading means evaluating Lisp code, and
evaluation order matters in Lisp.
> and if at that point
> further loading is ... required then that is all handled in
> that pack's source, nothing to bother the mere user with since
> s/he isn't even doing it.
I think you're wailing in the dark, here.
This is what such a file says. Do you think users
shouldn't be told this?
;;; Commentary:
;;
;; Extensions to library `ffap.el'.
;;
;; To use this library, add this to your initialization file.
;;
;; (require 'ffap-) ; Load this library.
;;
;; You should explicitly load *only* `ffap-.el', not also
;; `ffap.el' (this will automatically load `ffap.el').
> Or they are not redefining each other's stuff, are they?
They are. And at specific points.
`ffap-.el', for instance, redefines variable
`ffap-bindings', to make it user option.
And it adds a variable to let you inhibit FFAP
buffer-locally.
Then it loads standard library `ffap.el'.
Then it redefines function `ffap-guesser', to
take advantage of those vars.
https://www.emacswiki.org/emacs/download/ffap-.el
See also bug #26243:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25243
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 16004 bytes --]
next prev parent reply other threads:[~2022-02-05 17:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 12:47 (bounds-of-thing-at-point 'number) ⇒ nil Jean Louis
2022-02-04 13:20 ` tomas
2022-02-04 14:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-04 14:41 ` Robert Pluim
2022-02-04 14:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-04 21:29 ` [External] : " Drew Adams
2022-02-06 6:12 ` Jean Louis
2022-02-06 8:44 ` Drew Adams
2022-02-06 8:43 ` Drew Adams
2022-02-04 15:19 ` [External] : " Drew Adams
2022-02-04 15:35 ` Jean Louis
2022-02-04 15:50 ` Drew Adams
2022-02-04 16:55 ` Jean Louis
2022-02-04 21:29 ` Drew Adams
2022-02-04 21:46 ` Drew Adams
2022-02-05 0:54 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-05 1:36 ` Drew Adams
2022-02-05 1:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-05 17:27 ` Drew Adams [this message]
2022-02-06 15:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-06 6:08 ` Jean Louis
2022-02-06 7:02 ` Drew Adams
2022-02-06 8:10 ` Jean Louis
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=SJ0PR10MB5488A818581ED448E6B4CC0EF32A9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).