unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Kim <emacs18@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Adding the `prescient` packages to NonGNU ELPA?
Date: Sat, 10 Dec 2022 08:38:51 -0800	[thread overview]
Message-ID: <CAFq8O8vT5dXzWKrnSrP1RrYy2nLi0_jBzN-ArKhO4FFG3=gxkg@mail.gmail.com> (raw)
In-Reply-To: <jwva63vqosi.fsf-monnier+emacs@gnu.org>

I have not used Windows for so long that I hardly know anything about
it.  However following is found on straight.el documentation:

On Microsoft Windows, however, support for symlinks is not always
available, so the default value of straight-use-symlinks is nil on
that platform. That causes copying to be used instead, and an advice
is placed on find-file to cause the copied files to act as symlinks if
you try to edit them.

On Sat, 10 Dec 2022 at 07:12, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
> >> Ah, so `straight` relies on linking/copying the files.
> >> Do things like `C-h f` still jump to the actual VCS-controlled source?
> >>
> >> How does it make sure the copies are updated/sync'd when you edit the
> >> VCS-controlled sources?
> >
> > As far as I know straight does not do any copying at least not *.el
> > files.  It creates symlinks to *.el and other files so that `C-h f' jumps
>
> I see.  So Straight doesn't work under Windows?  Or does it then use
> copying (and `C-h f` doesn't jump to the source any more)?
>
>
>         Stefan
>



  reply	other threads:[~2022-12-10 16:38 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20  3:27 Adding the `prescient` packages to NonGNU ELPA? Okamsn
2022-11-20  9:24 ` Philip Kaludercic
2022-11-20 11:23   ` Stefan Kangas
2022-11-20 15:19     ` Stefan Monnier
2022-11-20 15:41       ` Philip Kaludercic
2022-11-21 21:17         ` Richard Stallman
2022-11-22 13:53           ` Akib Azmain Turja
2022-11-23 23:12             ` okamsn
2022-11-26  0:50               ` Richard Stallman
2022-11-20 17:10   ` Visuwesh
2022-11-20 18:39     ` Stefan Monnier
2022-12-16  9:41     ` North Year
2022-12-16 19:25       ` Philip Kaludercic
2022-12-17  3:28         ` Stefan Monnier
2022-12-17  9:17           ` Philip Kaludercic
2022-12-17 15:52             ` Stefan Monnier
2022-12-17 16:07               ` Philip Kaludercic
2022-12-17 16:24                 ` Philip Kaludercic
2022-12-17 18:01                   ` Okamsn
2022-12-17 18:08                     ` Philip Kaludercic
2022-12-17 18:39                     ` Stefan Monnier
2022-12-20  1:32                       ` Okamsn
2022-12-20  3:10                         ` Stefan Monnier
2022-11-20 17:42   ` Okamsn
2022-12-05  0:27     ` Okamsn
2022-12-05 15:21       ` Stefan Monnier
2022-12-09  3:58         ` Okamsn
2022-12-09 15:08           ` Stefan Monnier
2022-12-09 15:27             ` Philip Kaludercic
2022-12-10  4:10             ` Richard Kim
2022-12-10 15:12               ` Stefan Monnier
2022-12-10 16:38                 ` Richard Kim [this message]
2022-12-10 17:44                   ` Stefan Monnier
2022-12-05 17:21       ` Philip Kaludercic
2022-12-16  2:04         ` Okamsn
2022-12-16 19:26           ` Philip Kaludercic
2022-11-22 15:41   ` Jonas Bernoulli
2022-11-22 21:09     ` Stefan Monnier
2022-11-23  9:56       ` Jonas Bernoulli
2022-11-23 12:33         ` Stefan Monnier

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='CAFq8O8vT5dXzWKrnSrP1RrYy2nLi0_jBzN-ArKhO4FFG3=gxkg@mail.gmail.com' \
    --to=emacs18@gmail.com \
    --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 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).