* bug#6922: 23.1; Setting read-only property in an overlay has no effect @ 2010-08-26 14:46 MT 2011-12-10 12:09 ` Johan Bockgård 2016-01-18 21:29 ` Marcin Borkowski 0 siblings, 2 replies; 17+ messages in thread From: MT @ 2010-08-26 14:46 UTC (permalink / raw) To: 6922 If I create an overlay in a buffer and set the 'read-only' property to t, it seems to make no difference, and I can still make changes to the text in the region where the overlay is active. Setting other overlay properties does have an effect. Setting the read-only property as a text property however works as expected. To demonstrate: 1. Type some text in an empty buffer. 2. (setq overlay (make-overlay 1 10)) ; Creates an overlay in this buffer between positions 1-10 named 'overlay' 3. (overlay-put overlay 'read-only t) ; Applies the read-only property to this overlay. 4. Type some characters at the beginning of the buffer. Emacs doesn't complain that the text is read-only, and text is edited as normal. I do this instead: (put-text-property 1 10 'read-only t) ; Apply the read-only property as a text property rather than an overlay Now if I try typing text in the same region as before, Emacs prevents me from doing so and says 'Text is read-only'. In GNU Emacs 23.1.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) of 2010-03-29 on rothera, modified by Debian Windowing system distributor `The X.Org Foundation', version 11.0.10706000 configured using `configure '--build=i486-linux-gnu' '--host=i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' '--localstatedir=/var/lib' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes' '--enable-locallisppath=/etc/emacs23:/etc/emacs:/usr/local/share/emacs/23.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.1/site-lisp:/usr/share/emacs/site-lisp:/usr/share/emacs/23.1/leim' '--with-x=yes' '--with-x-toolkit=gtk' '--with-toolkit-scroll-bars' 'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' 'CFLAGS=-DDEBIAN -g -O2' 'LDFLAGS=-g' 'CPPFLAGS='' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: C value of $LC_TIME: en_DK.UTF-8 value of $LANG: en_IN.UTF-8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t Major mode: Fundamental Minor modes in effect: tooltip-mode: t tool-bar-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t blink-cursor-mode: t global-auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Recent input: M-x r e p o r t - e m a c s - b u g <return> Recent messages: Setting up ede... Loading `eieio': old-style backquotes detected! Setting up ede...done Setting up eieio...done Setting up semantic...done Setting up speedbar...done Setting up cedet-contrib...done Loading /etc/emacs/site-start.d/55ecb.el (source)...done For information about GNU Emacs and the GNU system, type C-h C-a. /usr/bin/mail is not an executable. Setting mail-interactive to t. -- http://www.fastmail.fm - Or how I learned to stop worrying and love email again ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 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 1 sibling, 0 replies; 17+ messages in thread From: Johan Bockgård @ 2011-12-10 12:09 UTC (permalink / raw) To: 6922 Cf. the discussion on emacs-devel http://lists.gnu.org/archive/html/emacs-devel/2008-01/msg01498.html ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 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 1 sibling, 1 reply; 17+ messages in thread From: Marcin Borkowski @ 2016-01-18 21:29 UTC (permalink / raw) To: 6922; +Cc: MT For the record, the problem persists in GNU Emacs 25.1.50.1. Neither seems there to be any change in the manual (as RMS suggested in the discussion at http://lists.gnu.org/archive/html/emacs-devel/2008-01/msg01598.html). Regards, Marcin Borkowski On 2010-08-26, at 17:46, "MT" <mt_void@warpmail.net> wrote: > If I create an overlay in a buffer and set the 'read-only' property to > t, it seems to make no difference, and I can still make changes to the > text in the region where the overlay is active. Setting other overlay > properties does have an effect. Setting the read-only property as a text > property however works as expected. > > To demonstrate: > 1. Type some text in an empty buffer. > 2. (setq overlay (make-overlay 1 10)) ; Creates an overlay in this > buffer between positions 1-10 named 'overlay' > 3. (overlay-put overlay 'read-only t) ; Applies the read-only property > to this overlay. > 4. Type some characters at the beginning of the buffer. Emacs doesn't > complain that the text is read-only, and text is edited as normal. > > I do this instead: > (put-text-property 1 10 'read-only t) ; Apply the read-only property > as a text property rather than an overlay > Now if I try typing text in the same region as before, Emacs prevents me > from doing so and says 'Text is read-only'. > > > > In GNU Emacs 23.1.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) > of 2010-03-29 on rothera, modified by Debian > Windowing system distributor `The X.Org Foundation', version > 11.0.10706000 > configured using `configure '--build=i486-linux-gnu' > '--host=i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib' > '--libexecdir=/usr/lib' '--localstatedir=/var/lib' > '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes' > '--enable-locallisppath=/etc/emacs23:/etc/emacs:/usr/local/share/emacs/23.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.1/site-lisp:/usr/share/emacs/site-lisp:/usr/share/emacs/23.1/leim' > '--with-x=yes' '--with-x-toolkit=gtk' '--with-toolkit-scroll-bars' > 'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' > 'CFLAGS=-DDEBIAN -g -O2' 'LDFLAGS=-g' 'CPPFLAGS='' > > Important settings: > value of $LC_ALL: nil > value of $LC_COLLATE: nil > value of $LC_CTYPE: nil > value of $LC_MESSAGES: nil > value of $LC_MONETARY: nil > value of $LC_NUMERIC: C > value of $LC_TIME: en_DK.UTF-8 > value of $LANG: en_IN.UTF-8 > value of $XMODIFIERS: nil > locale-coding-system: utf-8-unix > default-enable-multibyte-characters: t > > Major mode: Fundamental > > Minor modes in effect: > tooltip-mode: t > tool-bar-mode: t > mouse-wheel-mode: t > menu-bar-mode: t > file-name-shadow-mode: t > global-font-lock-mode: t > blink-cursor-mode: t > global-auto-composition-mode: t > auto-encryption-mode: t > auto-compression-mode: t > line-number-mode: t > transient-mark-mode: t > > Recent input: > M-x r e p o r t - e m a c s - b u g <return> > > Recent messages: > Setting up ede... > Loading `eieio': old-style backquotes detected! > Setting up ede...done > Setting up eieio...done > Setting up semantic...done > Setting up speedbar...done > Setting up cedet-contrib...done > Loading /etc/emacs/site-start.d/55ecb.el (source)...done > For information about GNU Emacs and the GNU system, type C-h C-a. > /usr/bin/mail is not an executable. Setting mail-interactive to t. ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-01-18 21:29 ` Marcin Borkowski @ 2016-01-20 18:00 ` Eli Zaretskii 2016-01-21 3:02 ` Richard Stallman ` (2 more replies) 0 siblings, 3 replies; 17+ messages in thread From: Eli Zaretskii @ 2016-01-20 18:00 UTC (permalink / raw) To: Marcin Borkowski, John Wiegley, Richard Stallman; +Cc: mt_void, 6922 > From: Marcin Borkowski <mbork@mbork.pl> > Date: Mon, 18 Jan 2016 22:29:53 +0100 > Cc: MT <mt_void@warpmail.net> > > For the record, the problem persists in GNU Emacs 25.1.50.1. Neither > seems there to be any change in the manual (as RMS suggested in the > discussion at > http://lists.gnu.org/archive/html/emacs-devel/2008-01/msg01598.html). What is the current consensus? should we adjust the documentation or fix the code? John? Richard? Which other overlay properties don't cause exactly the same effect as the corresponding text properties? ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-01-20 18:00 ` Eli Zaretskii @ 2016-01-21 3:02 ` Richard Stallman 2016-01-21 17:33 ` Eli Zaretskii 2016-02-07 22:24 ` John Wiegley 2016-02-08 16:04 ` John Wiegley 2 siblings, 1 reply; 17+ messages in thread From: Richard Stallman @ 2016-01-21 3:02 UTC (permalink / raw) To: Eli Zaretskii; +Cc: mbork, johnw, mt_void, 6922 [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] I have not been looking at this issue. Do I need to? -- Dr Richard Stallman President, Free Software Foundation (gnu.org, fsf.org) Internet Hall-of-Famer (internethalloffame.org) Skype: No way! See stallman.org/skype.html. ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-01-21 3:02 ` Richard Stallman @ 2016-01-21 17:33 ` Eli Zaretskii 2016-01-22 3:24 ` Richard Stallman 0 siblings, 1 reply; 17+ messages in thread From: Eli Zaretskii @ 2016-01-21 17:33 UTC (permalink / raw) To: rms; +Cc: mbork, johnw, mt_void, 6922 > From: Richard Stallman <rms@gnu.org> > CC: mbork@mbork.pl, johnw@gnu.org, 6922@debbugs.gnu.org, > mt_void@warpmail.net > Date: Wed, 20 Jan 2016 22:02:19 -0500 > > I have not been looking at this issue. Do I need to? There was an old discussion of this http://lists.gnu.org/archive/html/emacs-devel/2008-01/msg01598.html In that discussion, you said: It is no accident that read-only works only as a text property. It is tested for in textprop.c only as a text property. I am not sure that a read-only property on an overlay makes much sense. It is a strange thing to do. So I will fix the documentation. I'm asking if you still think the same. If so, perhaps you could try explaining why you do (in that old discussion, you said it was hard for you to put this into words). Thanks. ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-01-21 17:33 ` Eli Zaretskii @ 2016-01-22 3:24 ` Richard Stallman 2016-01-22 7:37 ` Eli Zaretskii 0 siblings, 1 reply; 17+ messages in thread From: Richard Stallman @ 2016-01-22 3:24 UTC (permalink / raw) To: Eli Zaretskii; +Cc: mbork, johnw, mt_void, 6922 [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > I am not sure that a read-only property on an overlay makes much sense. > It is a strange thing to do. So I will fix the documentation. I don't remember why I wrote that. It was 6 years ago. My guess is that I considered it strange to make certain text read-only temporarily. If it isn't supposed to change, it should never change, right? -- Dr Richard Stallman President, Free Software Foundation (gnu.org, fsf.org) Internet Hall-of-Famer (internethalloffame.org) Skype: No way! See stallman.org/skype.html. ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-01-22 3:24 ` Richard Stallman @ 2016-01-22 7:37 ` Eli Zaretskii 2016-01-22 10:59 ` Lars Magne Ingebrigtsen 0 siblings, 1 reply; 17+ messages in thread From: Eli Zaretskii @ 2016-01-22 7:37 UTC (permalink / raw) To: rms; +Cc: mbork, johnw, mt_void, 6922 > From: Richard Stallman <rms@gnu.org> > CC: mbork@mbork.pl, johnw@gnu.org, 6922@debbugs.gnu.org, > mt_void@warpmail.net > Date: Thu, 21 Jan 2016 22:24:37 -0500 > > > I am not sure that a read-only property on an overlay makes much sense. > > It is a strange thing to do. So I will fix the documentation. > > I don't remember why I wrote that. It was 6 years ago. My guess is > that I considered it strange to make certain text read-only > temporarily. If it isn't supposed to change, it should never change, > right? I see your point, thanks. What do others think? ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-01-22 7:37 ` Eli Zaretskii @ 2016-01-22 10:59 ` Lars Magne Ingebrigtsen 2016-01-22 12:58 ` Marcin Borkowski 0 siblings, 1 reply; 17+ messages in thread From: Lars Magne Ingebrigtsen @ 2016-01-22 10:59 UTC (permalink / raw) To: Eli Zaretskii; +Cc: mbork, johnw, mt_void, rms, 6922 Eli Zaretskii <eliz@gnu.org> writes: > What do others think? I think read-only overlays sound kinda nonsensical, too. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-01-22 10:59 ` Lars Magne Ingebrigtsen @ 2016-01-22 12:58 ` Marcin Borkowski 0 siblings, 0 replies; 17+ messages in thread From: Marcin Borkowski @ 2016-01-22 12:58 UTC (permalink / raw) To: Lars Magne Ingebrigtsen; +Cc: johnw, mt_void, rms, 6922 On 2016-01-22, at 11:59, Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: > Eli Zaretskii <eliz@gnu.org> writes: > >> What do others think? > > I think read-only overlays sound kinda nonsensical, too. Not necessarily. This is not the same, of course, but compare Dired to Wdired: the same text is sometimes read-only and sometimes not, and it does make a lot of sense. Another possible use-case: a feature like narrowing, but not making some text invisible, but read-only instead. (This might actually be useful, e.g. in Org-mode.) Of course, you could do this with text properties and not overlays, but what I'm saying is that the assumption "it [is] strange to make certain text read-only temporarily. If it isn't supposed to change, it should never change, right?" is false in general, even in current stock Emacs. Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-01-20 18:00 ` Eli Zaretskii 2016-01-21 3:02 ` Richard Stallman @ 2016-02-07 22:24 ` John Wiegley 2016-02-07 22:30 ` Marcin Borkowski 2016-02-18 5:12 ` Marcin Borkowski 2016-02-08 16:04 ` John Wiegley 2 siblings, 2 replies; 17+ messages in thread From: John Wiegley @ 2016-02-07 22:24 UTC (permalink / raw) To: Eli Zaretskii; +Cc: Marcin Borkowski, mt_void, Richard Stallman, 6922 >>>>> Eli Zaretskii <eliz@gnu.org> writes: > What is the current consensus? should we adjust the documentation or fix the > code? John? Richard? I think read-only overlays could be very useful. For example: 1. Create a command called `mask-regexp'. It creates read-only overlays for matching text throughout the buffer. 2. There should also be a way to add manual masks, using `mask-region'. 3. Now use `replace-string' or any other command to bulk transform text. However, masked text is not changed. 4. Then execute unmask-all, and the mask disappears. This method of editing is key to video editing workflows. I think the only reason I never thought to use it in Emacs is because it's never been there (and so never occurred to me until now). -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2 ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-02-07 22:24 ` John Wiegley @ 2016-02-07 22:30 ` Marcin Borkowski 2016-02-18 5:12 ` Marcin Borkowski 1 sibling, 0 replies; 17+ messages in thread From: Marcin Borkowski @ 2016-02-07 22:30 UTC (permalink / raw) To: John Wiegley; +Cc: mt_void, Richard Stallman, 6922 On 2016-02-07, at 23:24, John Wiegley <jwiegley@gmail.com> wrote: >>>>>> Eli Zaretskii <eliz@gnu.org> writes: > >> What is the current consensus? should we adjust the documentation or fix the >> code? John? Richard? > > I think read-only overlays could be very useful. For example: > > 1. Create a command called `mask-regexp'. It creates read-only overlays for > matching text throughout the buffer. > 2. There should also be a way to add manual masks, using `mask-region'. > 3. Now use `replace-string' or any other command to bulk transform text. > However, masked text is not changed. > 4. Then execute unmask-all, and the mask disappears. > > This method of editing is key to video editing workflows. I think the only > reason I never thought to use it in Emacs is because it's never been there > (and so never occurred to me until now). That's a fantastic idea! I envision "LaTeX-mask-environment", and bam! query-replace does not touch verbatim, for instance. That could be very useful! I did something similar with texmathp and math mode, but I like your approach with "masking". Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 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 1 sibling, 1 reply; 17+ messages in thread From: Marcin Borkowski @ 2016-02-18 5:12 UTC (permalink / raw) To: John Wiegley Cc: Richard Stallman, 6922, emacs-devel, Org-Mode mailing list, mt_void On 2016-02-07, at 23:24, John Wiegley <jwiegley@gmail.com> wrote: >>>>>> Eli Zaretskii <eliz@gnu.org> writes: > >> What is the current consensus? should we adjust the documentation or fix the >> code? John? Richard? > > I think read-only overlays could be very useful. For example: > > 1. Create a command called `mask-regexp'. It creates read-only overlays for > matching text throughout the buffer. > 2. There should also be a way to add manual masks, using `mask-region'. > 3. Now use `replace-string' or any other command to bulk transform text. > However, masked text is not changed. > 4. Then execute unmask-all, and the mask disappears. > > This method of editing is key to video editing workflows. I think the only > reason I never thought to use it in Emacs is because it's never been there > (and so never occurred to me until now). Hi, 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. Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-02-18 5:12 ` Marcin Borkowski @ 2016-02-18 16:52 ` Eli Zaretskii 2016-02-18 18:53 ` John Wiegley 0 siblings, 1 reply; 17+ messages in thread From: Eli Zaretskii @ 2016-02-18 16:52 UTC (permalink / raw) To: Marcin Borkowski; +Cc: johnw, mt_void, rms, 6922 > 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.) ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-02-18 16:52 ` Eli Zaretskii @ 2016-02-18 18:53 ` John Wiegley 0 siblings, 0 replies; 17+ messages in thread From: John Wiegley @ 2016-02-18 18:53 UTC (permalink / raw) To: Eli Zaretskii; +Cc: Marcin Borkowski, mt_void, rms, 6922 >>>>> Eli Zaretskii <eliz@gnu.org> writes: > 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. That said, I think the right way to implement clock-masking in Org would be to use an overlay whose existence is tied to the clock. A text-property might be incompatible with the way Org uses font-locking. -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2 ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-01-20 18:00 ` Eli Zaretskii 2016-01-21 3:02 ` Richard Stallman 2016-02-07 22:24 ` John Wiegley @ 2016-02-08 16:04 ` John Wiegley 2016-02-08 17:55 ` Eli Zaretskii 2 siblings, 1 reply; 17+ messages in thread From: John Wiegley @ 2016-02-08 16:04 UTC (permalink / raw) To: Eli Zaretskii; +Cc: Marcin Borkowski, mt_void, Richard Stallman, 6922 >>>>> Eli Zaretskii <eliz@gnu.org> writes: > What is the current consensus? should we adjust the documentation or fix the > code? John? Richard? Eli, can you fix to code to allows read-only overlays? Once you do, I'd like to write a mask.el module for GNU ELPA to support masked editing. Thanks, -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2 ^ permalink raw reply [flat|nested] 17+ messages in thread
* bug#6922: 23.1; Setting read-only property in an overlay has no effect 2016-02-08 16:04 ` John Wiegley @ 2016-02-08 17:55 ` Eli Zaretskii 0 siblings, 0 replies; 17+ messages in thread From: Eli Zaretskii @ 2016-02-08 17:55 UTC (permalink / raw) To: John Wiegley; +Cc: mbork, mt_void, rms, 6922 > From: John Wiegley <jwiegley@gmail.com> > Cc: Marcin Borkowski <mbork@mbork.pl>, Richard Stallman <rms@gnu.org>, 6922@debbugs.gnu.org, mt_void@warpmail.net > Date: Mon, 08 Feb 2016 11:04:06 -0500 > > >>>>> Eli Zaretskii <eliz@gnu.org> writes: > > > What is the current consensus? should we adjust the documentation or fix the > > code? John? Richard? > > Eli, can you fix to code to allows read-only overlays? Once you do, I'd like > to write a mask.el module for GNU ELPA to support masked editing. I'll take a look. Of course, if someone wants to beat me to it, feel free. ^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2016-02-18 18:53 UTC | newest] Thread overview: 17+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2016-02-18 18:53 ` John Wiegley 2016-02-08 16:04 ` John Wiegley 2016-02-08 17:55 ` Eli Zaretskii
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.