Am 24.06.2015 um 22:26 schrieb Lex Trotman:
I'm struggling to understand why there is any confusion, reload is an
editing action just like any other and can be undone like any other.
Seems much safer to me and exactly what to expect. It used to have a
side effect that was unexpected and nasty
On 25 June 2015 at 10:51, Matthew Brush mbr...@codebrainz.ca wrote:
On 2015-06-24 05:47 PM, Lex Trotman wrote:
[...]
I wonder if there's a more simple way to reduce confusion and increase
visibility other than an annoying dialog or document message. Maybe as a
separate action with a
On 2015-06-24 09:30 AM, Colomban Wendling wrote:
Le 24/06/2015 17:04, Thomas Martitz a écrit :
Hello
I have just noticed that current git, by default, doesn't prompt anymore
when reloading documents, even when they are changed.
I traced it back to the $SUBJECT commit. IMO it's fine to keep
On 2015-06-24 05:47 PM, Lex Trotman wrote:
[...]
I wonder if there's a more simple way to reduce confusion and increase
visibility other than an annoying dialog or document message. Maybe as a
separate action with a different name in the edit menu?
Menu, what menu? I use the toolbar
Hello
I have just noticed that current git, by default, doesn't prompt anymore
when reloading documents, even when they are changed.
I traced it back to the $SUBJECT commit. IMO it's fine to keep the undo
history on reload and not prompt, but it's not fine if the file is
currently modified
On 25 June 2015 at 15:19, Thomas Martitz ku...@rockbox.org wrote:
Am 25. Juni 2015 02:51:43 MESZ, schrieb Matthew Brush mbr...@codebrainz.ca:
On 2015-06-24 05:47 PM, Lex Trotman wrote:
[...]
I wonder if there's a more simple way to reduce confusion and
increase visibility other than an
Am 24.06.2015 um 18:30 schrieb Colomban Wendling:
Le 24/06/2015 17:04, Thomas Martitz a écrit :
Hello
I have just noticed that current git, by default, doesn't prompt anymore
when reloading documents, even when they are changed.
I traced it back to the $SUBJECT commit. IMO it's fine to keep
