From: Bastien <bzg@altern.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 19014@debbugs.gnu.org
Subject: bug#19014: 25.0.50; Disable Org, Tbl, & Text menu items that change buffer when read-only
Date: Tue, 18 Nov 2014 11:43:45 +0100 [thread overview]
Message-ID: <87d28k7pr2.fsf@bzg.ath.cx> (raw)
In-Reply-To: <fd823824-67e5-48be-9535-96c15f1c3992@default> (Drew Adams's message of "Mon, 10 Nov 2014 14:13:08 -0800 (PST)")
Hi Drew,
Drew Adams <drew.adams@oracle.com> writes:
> There are lots of menu items in the Org menu-bar menus (Org, Tbl, Text)
> that modify the buffer but are not disabled when the buffer is
> read-only. They should be - they are no-ops in this context.
>
> This is all the more important because there are still plenty of menu
> items for commands that are useful in a read-only buffer. Disabling the
> others makes those that are available more obvious and easier to select.
Do you often turn read-only on on Org buffers?
In what circumstances would users turn read-only on in Org buffers?
> That is what we do for the Edit menu, for example. You can use it as a
> model, here.
I understand the suggestion, I'm trying to see if this is important or
not. Thanks in advance for your feedback.
--
Bastien
next parent reply other threads:[~2014-11-18 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fd823824-67e5-48be-9535-96c15f1c3992@default>
2014-11-18 10:43 ` Bastien [this message]
2014-11-18 15:01 ` bug#19014: 25.0.50; Disable Org, Tbl, & Text menu items that change buffer when read-only Drew Adams
2020-05-22 12:31 ` Bastien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d28k7pr2.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=19014@debbugs.gnu.org \
--cc=drew.adams@oracle.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).