From: Eli Zaretskii <eliz@gnu.org>
To: dick <dick.r.chiang@gmail.com>,
Ioannis Kappas <ioannis.kappas@gmail.com>
Cc: 49786@debbugs.gnu.org
Subject: bug#49786: 28.0.50; [PATCH] package-install shouldn't change default-directory
Date: Fri, 30 Jul 2021 22:54:02 +0300 [thread overview]
Message-ID: <83zgu3poh1.fsf@gnu.org> (raw)
In-Reply-To: <87h7gb39bt.fsf@dick> (message from dick on Fri, 30 Jul 2021 15:12:06 -0400)
> From: dick <dick.r.chiang@gmail.com>
> Date: Fri, 30 Jul 2021 15:12:06 -0400
>
> Commit 606b783acb leverages a 2015 hack that extracts the
> package version from the buffer file name, only he has to
> explicitly `set-visited-file-name` to do it.
>
> `set-visited-file-name` has the adverse side effect of
> changing the default-directory, and that causes me problems.
Ioannis, could you please tell why you needed to call
set-visited-file-name there?
> If the ostensible reason for bug#48137 was to get the "lm"
> functions dos-aware, then why not do that instead of applying
> a workaround on top of a hack?
This was discussed in that bug, and the conclusion was that it's a
worse alternative than the solution eventually installed.
> * test/lisp/emacs-lisp/package-tests.el (package-test-install-file-EOLs):
> What is "mac" encoding? It doesn't work. The names of
> salient coding systems do not coincide with the predominant
> desktop operating systems.
The 'mac' encoding is documented in the ELisp manual. Please don't
remove its testing here.
next prev parent reply other threads:[~2021-07-30 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 19:12 bug#49786: 28.0.50; [PATCH] package-install shouldn't change default-directory dick
2021-07-30 19:54 ` Eli Zaretskii [this message]
2021-07-30 20:41 ` dick
2021-07-31 6:09 ` Eli Zaretskii
2021-07-30 20:50 ` Ioannis Kappas
2021-07-31 1:27 ` dick
2021-07-31 6:19 ` Eli Zaretskii
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=83zgu3poh1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49786@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--cc=ioannis.kappas@gmail.com \
/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.