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 13:41:53 +0200 [thread overview]
Message-ID: <831v8x6fb2.fsf@gnu.org> (raw)
In-Reply-To: <jwvtyluvvy5.fsf-monnier+inbox@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 6997@debbugs.gnu.org
> Date: Mon, 13 Sep 2010 11:27:30 +0200
>
> They can define new functions and variables, as well as load other
> files, and even set a few things up but only to *add* behavior, not to
> *change* behavior.
Not sure how instrumental that definition is. Doesn't addition
constitute a change?
Let's take a practical example: w32-convert-standard-filename. Do you
want it to become effective or not?
If your answer is NO, then what about someone (not called Stefan) who
wants to test some issue for which w32-convert-standard-filename must
be in effect?
> > IOW, can you come up with a general enough definition of the reason(s)
> > for loading w32-fns on non-w32 systems?
>
> The same reason why I might want to load diff-mode.el without ever
> wanting to use that mode.
>
> E.g. to complete function/variable names, or to browse customize data, ...
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-'?).
next prev parent reply other threads:[~2010-09-13 11:41 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 [this message]
2010-09-13 14:51 ` Stefan Monnier
2010-09-13 15:29 ` Eli Zaretskii
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=831v8x6fb2.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).