From: Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Heime <heimeborgia@protonmail.com>
Cc: Joel Reicher <joel.reicher@gmail.com>,
Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Running command makes buffers read-only
Date: Wed, 05 Feb 2025 13:31:56 +0000 [thread overview]
Message-ID: <TIpdXzeMN-lseT2IiH4B_VBBhEyiy2Pwkn1ojnXYTkcC_sR9GQKjj84MPhOMZTfctJmEaTvkmlQK4JpdRvZtP4-O1G5UfAN_sZT0UMmB7-g=@protonmail.com> (raw)
In-Reply-To: <sbPLy7-4Dr3zqKWlYE0ebnPzW13f11vegzYNz-3tUy7HHlnqUjL4PC8Ve0RKoCHpjHj5G1f-Kt5d7DaVowz0vGJWbq5rxfxasot1v5ETVAE=@protonmail.com>
Sent with Proton Mail secure email.
On Wednesday, February 5th, 2025 at 11:58 PM, Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
>
>
>
>
> Sent with Proton Mail secure email.
>
>
> On Wednesday, February 5th, 2025 at 10:14 PM, Joel Reicher joel.reicher@gmail.com wrote:
>
> > Heime via Users list for the GNU Emacs text editor
> > help-gnu-emacs@gnu.org writes:
> >
> > > I execute "M-x svm-clock", but if I run it again I get emacs
> > > complain that all the buffers are read-only, and thus do not get
> > > a new buffer with a new clock.
> >
> > What's your question?
> >
> > Regards, > - Joel
>
>
> I cannot do "M-x svm-clock" multiple times to got multiple clocks
> because the buffer read-only stops me.
From what I notice, the minibuffer has became read-only after the
first call to svm-clock.
prev parent reply other threads:[~2025-02-05 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 3:18 Running command makes buffers read-only Heime via Users list for the GNU Emacs text editor
2025-02-05 10:14 ` Joel Reicher
2025-02-05 11:58 ` Heime via Users list for the GNU Emacs text editor
2025-02-05 13:31 ` Heime via Users list for the GNU Emacs text editor [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='TIpdXzeMN-lseT2IiH4B_VBBhEyiy2Pwkn1ojnXYTkcC_sR9GQKjj84MPhOMZTfctJmEaTvkmlQK4JpdRvZtP4-O1G5UfAN_sZT0UMmB7-g=@protonmail.com' \
--to=help-gnu-emacs@gnu.org \
--cc=heimeborgia@protonmail.com \
--cc=joel.reicher@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.