> I'm curious why you think so. What kind of settings do you put in ~/.cvsrc?
> The nature of the ~/.cvsrc file is to contain settings which should
> basically always apply.
Nothing special:
cvs -z9
diff -u2
tag -c
edit -c
update -dP
release -d
status -v
"release -d", for example, is something
> I'm not going to fight over vc-cvs settings (no, really :-) but if we were
> creating VC from scratch, I would push for a `vc-cvs-use-cvsrc-settings',
> defaulting to nil. The equivalent functionality as of today is
> vc-cvs-global-settings '("-f").
I'm curious why you think so. What kind of se
> > (2) Customizations that the user makes inside Emacs should override
> > settings in .cvsrc. In some cases, it may be good or tolerable to
> > see a warning message if the settings are inconsistent, e.g. in
> > your case where Emacs and .cvsrc don't agree on the diff format.
>
> Ju
> (1) Settings from .cvsrc should be effective during VC commands, unless
> a particular VC command would not work with that setting, in
> which case VC must override it
I'm not going to fight over vc-cvs settings (no, really :-) but if we
were creating VC from scratch, I would push for a
On Wed, 2005-06-22 at 05:51 +0200, Juanma Barranquero wrote:
> Let's put it other way: even on normal situation, it seems safer to
> make VC *not* use customized defaults it knows nothing about (and
> which can cause trouble), and let the user who uses a .cvsrc and knows
> what he's doing to put a
> RET nil RET" *every time* he starts Emacs without loading .emacs.
Are you speaking seriously here?
The "emacs -Q" scenario is not a normal use scenario, AFAIK, so its
convenience doesn't really matter that much. At least not nearly as much as
the convenience of the normal situation.
S
> Are you speaking seriously here?
> The "emacs -Q" scenario is not a normal use scenario, AFAIK, so its
> convenience doesn't really matter that much. At least not nearly as much as
> the convenience of the normal situation.
Let's put it other way: even on normal situation, it seems safer to
mak
On 6/21/05, Stefan Monnier <[EMAIL PROTECTED]> wrote:
> I for one would be annoyed to have to re-specify in Emacs the options I've
> already set globally in my ~/.cvsrc.
You can always set `vc-cvs-global-switches' to nil in your .emacs. The
situation I'm trying to fix is precisely the one where t
> I was running "emacs.exe -Q" today and was puzzled to see that the
> output of `vc-diff' talked about "conflicting specifications of output
> style", until I remembered that I have an entry on ~/.cvsrc which
> says: "diff -u2", and the default style for VC is "-c".
> So the question is: why does
