From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 6997@debbugs.gnu.org
Subject: bug#6997: Loading w32-fns under X11 signals an error
Date: Mon, 13 Sep 2010 17:29:19 +0200 [thread overview]
Message-ID: <83hbht4q7k.fsf@gnu.org> (raw)
In-Reply-To: <jwvvd69vh92.fsf-monnier+inbox@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 6997@debbugs.gnu.org
> Date: Mon, 13 Sep 2010 16:51:20 +0200
>
> I'm not sure exactly what you're trying to argue here.
I'm not trying to argue at all, just trying to understand what you
want to be done about w32-fns.el.
> It's been policy
> for a long time now that loading files should be harmless, so many files
> were changed so that (load "foo") doesn't enable foo-mode any more, but
> instead just defines foo-mode (and then foo-mode is marked auto-loaded
> so the user can just call (foo-mode 1) rather than (load "foo") in his
> .emacs).
> Clearly, load foo.el will make changes in that it will define new
> functions and variables, may add things to debug-ignored-errors and
> whatnot.
But many .el files have top-level expressions other than defun and
defvar. These don't just define functions and variables, they
actually change the behavior. w32-fns.el does that as well, but it is
not the only one. I understand that you want all these top-level
expressions be conditioned by w32?
> > That's rather a narrow need. Sounds like lots of labor to gain very
> > little (why does it matter to have symbols that begin with a `w32-'?).
>
> Yes, it's a lot of work for fairly little gain. Note that I bumped into
> it because my code couldn't care less that "w32-" is special, not
> because I specifically wanted to have symbols starting with "w32-".
How about teaching your code not to load any file that has w32 (or
dos, or ns, for that matter) in its name? Or perhaps we should have a
list of platform-specific .el files that are not "safe" for loading on
other platforms? Maybe that will be easier than modifying all those
to make them "Stefan-harmless"?
next prev parent reply other threads:[~2010-09-13 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 9:33 bug#6997: Loading w32-fns under X11 signals an error Stefan Monnier
2010-09-11 21:41 ` Juanma Barranquero
2010-09-13 7:18 ` Eli Zaretskii
2010-09-13 9:27 ` Stefan Monnier
2010-09-13 11:41 ` Eli Zaretskii
2010-09-13 14:51 ` Stefan Monnier
2010-09-13 15:29 ` Eli Zaretskii [this message]
2010-09-14 9:32 ` Stefan Monnier
2010-09-14 11:59 ` Juanma Barranquero
2017-12-15 2:21 ` Glenn Morris
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=83hbht4q7k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6997@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).