From: Eli Zaretskii <eliz@gnu.org>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: johnw@gnu.org, mt_void@warpmail.net, rms@gnu.org, 6922@debbugs.gnu.org
Subject: bug#6922: 23.1; Setting read-only property in an overlay has no effect
Date: Thu, 18 Feb 2016 18:52:43 +0200 [thread overview]
Message-ID: <83y4ait0ys.fsf@gnu.org> (raw)
In-Reply-To: <87h9h6zjn9.fsf@mbork.pl> (message from Marcin Borkowski on Thu, 18 Feb 2016 06:12:42 +0100)
> From: Marcin Borkowski <mbork@mbork.pl>
> Cc: Eli Zaretskii <eliz@gnu.org>, Richard Stallman <rms@gnu.org>,
> 6922@debbugs.gnu.org, mt_void@warpmail.net,
> Org-Mode mailing list <emacs-orgmode@gnu.org>, emacs-devel <emacs-devel@gnu.org>
> Date: Thu, 18 Feb 2016 06:12:42 +0100
>
> I just realized that this idea could be /extremely/ useful. Here's the
> case: I start a clock in Org-mode (C-c C-x C-i), and an entry with the
> starting time is added in the :LOGBOOK: drawer (and btw, it is
> invisible). While working on the file, I hit C-/ (undo) once too many,
> and the entry disappears (and this fact is still invisible to me!).
> Then, after some more work, I stop the clock only to see "org-clock-out:
> Clock start time is gone", and my clock is still going on (!).
>
> While the last thing (about the clock still going on) is probably an
> Org-mode bug (I'll propbably report it later "officially", I'm now
> Cc-ing this message to the Org-mode ML), the whole experience (and yes,
> it happened to me) is /very/ confusing.
>
> When read-only properties and masking are here, Org could just mark the
> half-done entry as read-only. I suspect that trying to undo it would
> perhaps trigger some error, which could be confusing, but it would be
> still better than silently removing a vital information.
If you are arguing for having a feature that marks some portion of
buffer text read-only, then we already have that: the 'read-only' text
property. The issue in this discussion is whether we should _also_
have a similar overlay property.
(Please don't cross-post to the bug tracker and to emacs-devel.)
next prev parent reply other threads:[~2016-02-18 16:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 14:46 bug#6922: 23.1; Setting read-only property in an overlay has no effect MT
2011-12-10 12:09 ` Johan Bockgård
2016-01-18 21:29 ` Marcin Borkowski
2016-01-20 18:00 ` Eli Zaretskii
2016-01-21 3:02 ` Richard Stallman
2016-01-21 17:33 ` Eli Zaretskii
2016-01-22 3:24 ` Richard Stallman
2016-01-22 7:37 ` Eli Zaretskii
2016-01-22 10:59 ` Lars Magne Ingebrigtsen
2016-01-22 12:58 ` Marcin Borkowski
2016-02-07 22:24 ` John Wiegley
2016-02-07 22:30 ` Marcin Borkowski
2016-02-18 5:12 ` Marcin Borkowski
2016-02-18 16:52 ` Eli Zaretskii [this message]
2016-02-18 18:53 ` John Wiegley
2016-02-08 16:04 ` John Wiegley
2016-02-08 17:55 ` 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=83y4ait0ys.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6922@debbugs.gnu.org \
--cc=johnw@gnu.org \
--cc=mbork@mbork.pl \
--cc=mt_void@warpmail.net \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).