"R. Lahaye" <[EMAIL PROTECTED]> writes:
| Wouldn't that be a better option for read-only documents?
| Or am I overlooking something?
Yes. The "buffer-toggle-read-only" command.
Lgb
> "R" == R Lahaye <[EMAIL PROTECTED]> writes:
R> Is this really necessary? I suggest to have a more "liberal" access
R> to read-only documents (for example everything you can do with a
R> regular document, but skip the auto/emergency saves).
You can always use 'buffer-toggle-read-only' to av
Am I right that the only problem with editing read-only files
are the 'quiet' auto and emergency saves done by LyX?
If that's true:
Instead of disabling all sorts of edit/ok/apply buttons, one should
ONLY block the auto/emergency saves while working with a read-only
document. Pop up a window tha
On Thu, 20 Jul 2000, Kayvan A. Sylvan wrote:
> On Fri, Jul 21, 2000 at 03:04:42PM +0900, R. Lahaye wrote:
>
> > Currently I have to make a copy of the read-only file to
> > my homedir first. Play with it and then delete it again.
> > This is not impossible, but a bit silly.
> >
> > Is this real
On Fri, Jul 21, 2000 at 03:04:42PM +0900, R. Lahaye wrote:
> Currently I have to make a copy of the read-only file to
> my homedir first. Play with it and then delete it again.
> This is not impossible, but a bit silly.
>
> Is this really necessary? I suggest to have a more
> "liberal" access to
Hello,
I've installed LyX in /usr/local/... as root.
As a regular user I don't have write permission to
the documentation, as it should be on a decent OS.
However, LyX disables all editing tools for read-only
documents, and this is a nuissance when reading (and
inspecting) readonly (documentati
