unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: require (was: Re: Hooks in minor modes)
Date: Sat, 1 May 2021 08:49:45 +0300	[thread overview]
Message-ID: <YIzr+Sk6q10HyRcr@protected.localdomain> (raw)
In-Reply-To: <87eeerfge1.fsf@zoho.eu>

* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-05-01 03:27]> Well yes, but that is the _intention_, so I don't understand
> why you say that. If I OTOH would want ~/tmp why would I try
> to point to that with "."? why would I do that?
> instead I would add it hard-coded. but I only want ~/tmp when
> that's where I am and that is what "." means.

Sure I got it you keep "." as it is for you a way to load scripts from
current directory wherever you are. That way you load those from
directory.

To me that defeats the purpose of load-path, as it is normally used
from scripts, loading or requiring should take place regardless of
current directory, it is not much interactive.

By the way when I am in Dired, I am thus changing current directory,
and when I wish to load file not in load-path, I just use key `L' and
load arbitrary file interactively.


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/
https://rms-support-letter.github.io/




  reply	other threads:[~2021-05-01  5:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 23:33 Hooks in minor modes steve-humphreys
2021-04-29 23:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-30  3:31 ` Stefan Monnier
2021-04-30  4:12   ` steve-humphreys
2021-04-30  4:33     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-30  4:43       ` require (was: Re: Hooks in minor modes) Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-30  5:03         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-30  5:44           ` Jean Louis
2021-04-30 21:53             ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-30 23:16               ` Jean Louis
2021-05-01  0:26                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-01  5:49                   ` Jean Louis [this message]
2021-05-01  6:09                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-01  9:23                       ` Jean Louis
2021-05-04  2:29                         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-04  5:40                           ` Yuri Khan
2021-05-04  6:02                             ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-30 17:27           ` FW: [External] : " Drew Adams
2021-04-30 22:17             ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-01  0:49               ` FW: " Drew Adams
2021-05-01  0:53                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-30  5:17     ` Hooks in minor modes Stefan Monnier
2021-04-30  5:32       ` Emanuel Berg via Users list for the GNU Emacs text editor

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=YIzr+Sk6q10HyRcr@protected.localdomain \
    --to=bugs@gnu.support \
    --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).