unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : (bounds-of-thing-at-point  'number) ⇒ nil
Date: Sun, 06 Feb 2022 16:48:42 +0100	[thread overview]
Message-ID: <87h79c6lnp.fsf@zoho.eu> (raw)
In-Reply-To: SJ0PR10MB5488A818581ED448E6B4CC0EF32A9@SJ0PR10MB5488.namprd10.prod.outlook.com

Drew Adams wrote:

> 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').

In general I think if they have to be told that, one hasn't
written good enough code.

If A and B don't rely on each other, obviously the order does
not matter.

If B relies on A, then whenever B is loaded it will just
`require' A so again the order won't matter, or rather, the
correct order is not an issue with A, and implicit with B.

>> Or they are not redefining each other's stuff, are they?
>
> They are.  And at specific points.

Then you ask for trouble. And not just for this reason.

But then yes, if B relies on A and B redefines stuff in A, if
one intends to use those redefined methods while still
referring to them with A's names, then one cannot load A after
loading B ...

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2022-02-06 15:48 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
2022-02-06 15:48                     ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
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=87h79c6lnp.fsf@zoho.eu \
    --to=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).