[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Inhibiting read-only
From: |
Eli Zaretskii |
Subject: |
Re: Inhibiting read-only |
Date: |
Thu, 20 Jun 2013 18:56:22 +0300 |
> From: Lars Magne Ingebrigtsen <address@hidden>
> Date: Thu, 20 Jun 2013 10:44:25 +0200
> Cc: James Cloos <address@hidden>, address@hidden
>
> I like `read-only' buffers -- they have an obvious interface. If the
> user decides to switch read-only off (which I sometimes do in otherwise
> non-editable buffers) to do some weird ad-hoc editing, there's a
> standard, convenient key-stroke for that.
>
> So if there were a `inhibit-read-only' text property, we could avoid
> doing all these tricks with `before-change-function' and the like -- we
> could just make the buffer read-only, put the text property on the bits
> that aren't read-only, and we'd be done. And there would be less user
> confusion.
>
> I can have a go at implementing this if it sounds like a workable idea,
> although that part of the code is completely unfamiliar to me...
Can you explain once more why putting the read-only property on all
the text except those parts you want to be modifiable is not what you
want?
- Re: Inhibiting read-only, (continued)
- Re: Inhibiting read-only, Juanma Barranquero, 2013/06/19
- Re: Inhibiting read-only, James Cloos, 2013/06/19
- Re: Inhibiting read-only, Lars Magne Ingebrigtsen, 2013/06/19
- Re: Inhibiting read-only, Stefan Monnier, 2013/06/19
- Re: Inhibiting read-only,
Eli Zaretskii <=
- Re: Inhibiting read-only, Lars Magne Ingebrigtsen, 2013/06/20
- Re: Inhibiting read-only, Eli Zaretskii, 2013/06/20
- Re: Inhibiting read-only, Lars Magne Ingebrigtsen, 2013/06/20
- Re: Inhibiting read-only, Eli Zaretskii, 2013/06/20
- Re: Inhibiting read-only, Lars Magne Ingebrigtsen, 2013/06/20
- Re: Inhibiting read-only, Eli Zaretskii, 2013/06/20
- Re: Inhibiting read-only, Stephen J. Turnbull, 2013/06/21