[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnulib-tool: don't use hard links
From: |
Bruno Haible |
Subject: |
Re: gnulib-tool: don't use hard links |
Date: |
Sun, 21 May 2017 21:54:32 +0200 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-75-generic; KDE/5.18.0; x86_64; ; ) |
Hi Paul,
> > When you set vc-follow-symlinks to nil,
>
> I don't want to do that. I want to edit just one file and have it affect
> everything I'm working on
"gnulib-tool -S" and (setq vc-follow-symlinks nil) achieves just that, as far
as I can see from experiments.
> without hassling me about it.
You could get rid of the useless warning
"Warning: symbolic link to Git-controlled source file"
since you are close to the Emacs developers.
> Better, I suppose, would be setting vc-follow-symlinks to t,
When you set vc-follow-symlinks to t, then at the next file you open, it shows
you the directory of the gnulib checkout, not the testdir's contents. Which is
usually not what you want.
> for other
> stuff that I'm working on, where the default value 'ask' is often the right
> thing to do.
Well, in this case, if for other projects 'ask' is better, I'll implement
the options -h / --hardlink, -H / --more-hardlinks.
Bruno
- gnulib build/test ?, Tim Rühsen, 2017/05/16
- Re: gnulib build/test ?, Bruno Haible, 2017/05/16
- Re: gnulib build/test ?, Tim Rühsen, 2017/05/16
- Re: gnulib build/test ?, Tim Rühsen, 2017/05/16
- Re: gnulib build/test ?, Bruno Haible, 2017/05/17
- Re: gnulib build/test ?, Tim Rühsen, 2017/05/17
- gnulib-tool: don't use hard links, Bruno Haible, 2017/05/20
- Re: gnulib-tool: don't use hard links, Paul Eggert, 2017/05/20
- Re: gnulib-tool: don't use hard links, Bruno Haible, 2017/05/21
- Re: gnulib-tool: don't use hard links, Paul Eggert, 2017/05/21
- Re: gnulib-tool: don't use hard links,
Bruno Haible <=
- Re: gnulib-tool: don't use hard links, Bruno Haible, 2017/05/21
- Re: gnulib-tool: don't use hard links, Paul Eggert, 2017/05/21