Save on save

[racoon]

On 2020-03-19 15:21, Scott Kostyshak wrote:
> On Thu, Mar 19, 2020 at 03:14:00PM +0100, racoon wrote:
>> On 2020-03-19 15:08, Scott Kostyshak wrote:
>>> On Thu, Mar 19, 2020 at 09:53:19AM -0400, Richard Kimberly Heck wrote:
>>>> On 3/19/20 9:46 AM, racoon wrote:
>>>>> On 2020-03-19 14:43, Richard Kimberly Heck wrote:
>>>>>> On 3/19/20 5:43 AM, Daniel wrote:
>>>>>>> All applications (Libre Writer, Pages, Visual Studio Code, TextEdit,
>>>>>>> etc.) I tested save my documents whenever I press ctrl|cmd+S or choose
>>>>>>> Save from the menu. This can be seen, for example, from the modified
>>>>>>> date being updated.
>>>>>>>
>>>>>>> The only exception are MS office (which does not save and not gray out
>>>>>>> the Save menu) and LyX (which does not save but does at least gray out
>>>>>>> the Save menu). Is there a particular reason LyX behaves in this way?
>>>>>>> Is there a way, I can change this behavior and force a save?
>>>>>>
>>>>>> You mean if the document is not dirty? Hit "s", backspace, then save.
>>>>>> I.e, make it dirty.
>>>>>>
>>>>>> Riki
>>>>>>
>>>>>>
>>>>>
>>>>> I find it hard to remember doing this. So, I would like to change LyX's
>>>>> Save command to a forced saving.
>>>>>
>>>>> Maybe there is a nice command sequence that renders the document dirty,
>>>>> maybe via some change; undoes the change, if there was one made; saves?
>>>>
>>>> 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.
>>>
>>> It's always useful to have a use case for motivation. racoon, what is
>>> your use case? I've come across this when I wanted to do something like
>>> open a 2.2.x file in 2.3.x and save it just to update the file format. I
>>> then commit those changes in git, and then I make a change. That ways I
>>> separate out the format update from the change.
>>>
>>> Scott
>>>
>>
>> My use case is that I often change the closed/open state of insets which
>> does not render the document dirty. But I still want LyX to remember
>> these changes. And I often forget to render it artificially dirty before
>> saving.
>
> Ah, that makes sense. I now remember having the same issue
> (closing/opening insets).

Bold move: https://www.lyx.org/trac/ticket/2993#comment:13. Feel free to
close again. :)

Daniel