From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Since some months, my .el files are read only, why?
Date: Fri, 26 Jul 2024 12:28:35 +0300 [thread overview]
Message-ID: <ZqNsQ15bkR405CuE@lco2> (raw)
In-Reply-To: <861q3pfffx.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2024-07-19 21:04]:
> > Date: Wed, 17 Jul 2024 17:46:09 +0300
> > From: Jean Louis <bugs@gnu.support>
> > Cc: help-gnu-emacs@gnu.org
> >
> > * Eli Zaretskii <eliz@gnu.org> [2024-07-17 14:36]:
> > > > I have renamed RCS directory and now those files do not appear read only.
> > > >
> > > > But I wonder how is that when rcs command was not installed.
> > >
> > > That's clear to me: when you check-in a file into RCS, it is made
> > > read-only in the filesystem. That's how RCS works, always has.
> >
> > Mystery solved.
> >
> > Question is if it should be that way even if `rcs' command is not installed.
>
> Emacs tries to be efficient, so it takes the existence of the RCS
> subdirectory and the files in it as the indication of the fact that
> the file is managed by RCS. This is faster than invoking the RCS
> programs.
Don't you think that some kind of warning shall be given about it, like in *Messages* that it did not find rcs command and that files are made read-only?
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
✡️🛡️ Proudly standing with Israel, a nation rooted in history and culture. Let's condemn hatred and promote understanding.
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2024-07-26 9:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 11:51 Since some months, my .el files are read only, why? Jean Louis
2024-07-06 11:58 ` Eli Zaretskii
2024-07-06 12:04 ` Eli Zaretskii
2024-07-06 12:47 ` Jean Louis
2024-07-06 13:55 ` Eli Zaretskii
2024-07-07 6:46 ` Jean Louis
2024-07-10 6:28 ` Emanuel Berg
2024-07-11 18:00 ` Emanuel Berg
2024-07-14 6:00 ` Jean Louis
2024-07-17 9:54 ` Robert Pluim
2024-07-17 13:31 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-07-17 11:34 ` Eli Zaretskii
2024-07-17 14:46 ` Jean Louis
2024-07-19 17:40 ` Eli Zaretskii
2024-07-26 9:28 ` Jean Louis [this message]
2024-07-30 16:44 ` 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
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=ZqNsQ15bkR405CuE@lco2 \
--to=bugs@gnu.support \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).