From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: Managing environments (Python venv, guix environment, etc.)
Date: Sat, 23 Jul 2016 10:10:21 +0300 [thread overview]
Message-ID: <83oa5ox21u.fsf@gnu.org> (raw)
In-Reply-To: <jwvwpkd4eo1.fsf-monnier+gmane.emacs.devel@gnu.org> (message from Stefan Monnier on Fri, 22 Jul 2016 16:19:38 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Fri, 22 Jul 2016 16:19:38 -0400
>
> > The problem is that paths passed to find-file-name-handler, such as
> > default-directory, are not necessarily canonical paths.
>
> Yes, that's indeed a problem. In practice it tends to work OK, tho,
> because file and directory names to be constructed from each other, so
> even if there are many different ways to name a particular directory,
> there's typically only one that's used in a particular Emacs session.
>
> And in any case it'd be good to fix the cases where we end up using
> different names for the same dir (because they end up bumping into
> similar problems).
Actually, I don't like to see any feature, let alone a core one, use
file-name-handler-alist for local files. Lots of code in Emacs,
including primitives, really handle such files as remote, so the
results are likely to be incorrect and subtly broken.
> > OK, I'll wait until John expresses his thoughts. (Possibly after the
> > release?)
>
> You might also contact the authors of python's virtualenv support (and
> anything else related) to get their opinions as supporting evidence for
> the benefits of your suggestion.
I always thought that features like this one should use and extent
the infrastructure in project.el. And yet Dmitry is silent in this
discussion. What am I missing?
next prev parent reply other threads:[~2016-07-23 7:10 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 21:36 Managing environments (Python venv, guix environment, etc.) sbaugh
2016-07-15 16:26 ` Stefan Monnier
2016-07-17 22:41 ` sbaugh
2016-07-18 10:15 ` Andreas Röhler
2016-07-18 14:46 ` Stefan Monnier
2016-07-18 19:13 ` sbaugh
2016-07-19 13:39 ` Stefan Monnier
2016-07-24 3:35 ` Dmitry Gutov
2016-07-24 8:25 ` sbaugh
2016-07-24 23:08 ` Dmitry Gutov
2016-07-21 0:32 ` sbaugh
2016-07-22 20:19 ` Stefan Monnier
2016-07-23 7:10 ` Eli Zaretskii [this message]
2016-07-24 3:26 ` Dmitry Gutov
2016-07-24 8:25 ` sbaugh
2016-07-24 14:28 ` Eli Zaretskii
2016-07-24 17:45 ` sbaugh
2016-07-24 17:58 ` Eli Zaretskii
2016-07-24 19:05 ` Spencer Baugh
2016-07-24 19:36 ` Eli Zaretskii
2016-07-25 4:50 ` sbaugh
2016-07-25 17:04 ` Eli Zaretskii
2016-07-28 0:47 ` sbaugh
2016-07-24 23:04 ` Dmitry Gutov
2016-07-25 2:37 ` Eli Zaretskii
2016-07-25 5:01 ` sbaugh
2016-07-25 17:06 ` Eli Zaretskii
2016-07-25 7:07 ` Michael Albinus
2016-07-25 12:49 ` Dmitry Gutov
2016-07-25 13:03 ` Michael Albinus
2016-07-25 13:06 ` Dmitry Gutov
2016-07-25 13:41 ` Stefan Monnier
2016-07-28 0:02 ` sbaugh
2016-07-28 9:34 ` Michael Albinus
2016-07-28 14:42 ` Eli Zaretskii
2016-07-29 17:59 ` sbaugh
2016-07-29 18:59 ` Eli Zaretskii
2016-07-29 19:20 ` Stefan Monnier
2016-07-30 6:57 ` Eli Zaretskii
2016-07-30 14:42 ` Stefan Monnier
2016-07-30 15:56 ` Eli Zaretskii
2016-07-29 20:57 ` sbaugh
2016-07-30 7:34 ` Eli Zaretskii
2016-07-30 13:30 ` sbaugh
2016-07-30 16:17 ` Eli Zaretskii
2016-07-30 11:24 ` Michael Albinus
2016-07-29 18:42 ` Stefan Monnier
2016-07-29 19:03 ` Eli Zaretskii
2016-07-26 2:36 ` Stefan Monnier
2016-07-24 14:24 ` Eli Zaretskii
2016-07-25 0:05 ` Dmitry Gutov
2016-07-25 17:00 ` Eli Zaretskii
2016-07-26 2:08 ` Dmitry Gutov
2016-07-26 3:06 ` Stefan Monnier
2016-07-26 10:45 ` Michael Albinus
2016-07-26 12:46 ` Stefan Monnier
2016-07-26 14:49 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2016-07-28 10:01 Spencer Baugh
[not found] <87shuuvzz6.fsf@totally-fudged-out-message-id>
2016-07-28 10:08 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83oa5ox21u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.