On Saturday, October 13, 2018 at 12:39:37 PM UTC+1, Edward K. Ream wrote:
>
>
>
> On Sat, Oct 13, 2018 at 6:24 AM jkn <[email protected] <javascript:>>
> wrote:
>
> Occasionally I would like to protect myself from changing any files within
>> Leo. Would it be possible to have a command-line option for all files to be
>> open read-only?
>>
>
> I think so. --read-only would disable the save-* commands. I've just
> created #995 <https://github.com/leo-editor/leo-editor/issues/995> for
> this.
>
> But suppose you forget that --read-only is in effect. You write code for
> an hour before trying to save. Leo tells you that you can't save. Now you
> have to remember what changes you made, open another copy of Leo, and save
> your changes. This might dissuade you from using --read-only.
>
> Another option is to use git to manage your files...
>
> Edward
>
Hi Edward
Thanks for #995. Yes, you'd ideally want some clear way of indicating
that Leo was operating in this mode. Perhaps a different (configurable?)
window border colour, or similar. Though ... do people really 'write code
for an hour before trying to save'?
In part this suggestion is de to my workflow re. OwnCloud and Leo files,
and my ... discomfort ... with the way Leo treats updated files (or at
least the prompts thereof). Git is another method, although FWIW I think it
doesn't work well over owncloud.
Regards
jon N
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
