From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Since some months, my .el files are read only, why?
Date: Sat, 06 Jul 2024 16:55:55 +0300 [thread overview]
Message-ID: <861q464ob8.fsf@gnu.org> (raw)
In-Reply-To: <Zok831m4RAWdRGS_@lco2> (message from Jean Louis on Sat, 6 Jul 2024 15:47:27 +0300)
> Date: Sat, 6 Jul 2024 15:47:27 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: help-gnu-emacs@gnu.org
>
> * Eli Zaretskii <eliz@gnu.org> [2024-07-06 15:05]:
> > > Date: Sat, 06 Jul 2024 14:58:57 +0300
> > > From: Eli Zaretskii <eliz@gnu.org>
> > >
> > > Details, please:
> > >
> > > . what Emacs version?
> > > . what are "my .el files"? are they those which came with Emacs,
> > > something that you yourself wrote, something else?
> > > . how do you visit them?
>
> Those are files I write.
>
> > . what does "ls -l" say about these files?
>
> -rw-r--r-- 1 lco lco 682090 Jul 6 15:25 rcd-cf.el
> -rw-r--r-- 1 lco lco 112801 Jul 3 17:37 rcd-utilities.el
>
> That is example.
You didn't say what Emacs version is that.
> I just opened rcd-utilities.el with `emacs -Q' and it is read-only.
>
> But some other files are not read-only.
What's the difference between the two groups? Does "ls -l" show the
same for files from both groups?
next prev parent reply other threads:[~2024-07-06 13:55 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 [this message]
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
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=861q464ob8.fsf@gnu.org \
--to=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).