Save on save

[racoon]

On 2020-03-27 17:52, racoon wrote:
> On 2020-03-27 17:41, Richard Kimberly Heck wrote:
>> On 3/27/20 4:21 AM, Daniel wrote:
>>> On 2020-03-19 15:03, racoon wrote:
>>>> On 2020-03-19 14:53, Richard Kimberly Heck wrote:
>>>>> Yes, you could assign something like "command-sequence self-insert s;
>>>>> char-delete-backward; buffer-write" to Ctrl-S. Undo won't work,
>>>>> because
>>>>> then the document isn't dirty again.
>>>>>
>>>>> Riki
>>>>>
>>>>>
>>>>
>>>> Unfortunately, when the settings dialog is closed and re-opened
>>>> everything that comes after the first semi-colon is chopped off. Is
>>>> that
>>>> a bug?
>>>
>>> Oddly enough, it is possible to use similar command sequences. So, the
>>> problem isn't general. For example,
>>>
>>> command-sequence self-insert .; space-insert normal
>>>
>>> just works fine (see https://www.lyx.org/trac/ticket/11798#comment:6).
>>> I don't know what the difference might be.
>>
>> Don't see it here.
>>
>> You can put it manually into your user.bind file if need be.
>>
>> Riki
>
> Thanks, that helped. And I figured out what the problem was. I copied
> the command from your email not knowing that my email program had
> inserted a line-break after the first command in the sequence.
> Unfortunately, the input box in the shortcut editor masked this. I guess
> it would be better if text pasted into the input box was cleaned of
> characters it does not support rather than just hiding them.
>
> Daniel


Seems like at least this particular command sequence is not such a good
idea. I just realized that it wrecks havoc if there is an active
selection of text because the text gets removed.

But it seems any change to the document will likely have an effect
cannot be easily reverted by a another command. This does not only
concern deleted text but also added tracked changes, e.g. by inserting
an inset.

So, I guess there is no way to get this without proper implementation,
right?

Daniel