On Sun, Feb 20, 2022 at 07:51:43PM +0100, Jean-Marc Lasgouttes wrote:
>
> Le 18/02/2022 à 17:18, Scott Kostyshak a écrit :
> > In whatever part of LyX's code that marks a buffer as dirty, should we
> > assert that the document is not read-only?
> >
> > If I open the User Guide from the Help
Le 18/02/2022 à 17:18, Scott Kostyshak a écrit :
In whatever part of LyX's code that marks a buffer as dirty, should we
assert that the document is not read-only?
If I open the User Guide from the Help menu, editing is disabled. But if I run:
command-sequence inset-forall Caption
In whatever part of LyX's code that marks a buffer as dirty, should we
assert that the document is not read-only?
If I open the User Guide from the Help menu, editing is disabled. But if I run:
command-sequence inset-forall Caption char-delete-forward; statistics; undo
The buffer is marked as
