On 2020-03-31 17:02, Richard Kimberly Heck wrote:
On 3/31/20 10:37 AM, Daniel wrote:
On 2020-03-31 12:40, Jürgen Spitzmüller wrote:
Am Dienstag, den 31.03.2020, 11:56 +0200 schrieb Daniel:
Wouldn't that cause headaches when opening the document on another
computer? Or what is a session?
On 3/31/20 10:37 AM, Daniel wrote:
> On 2020-03-31 12:40, Jürgen Spitzmüller wrote:
>> Am Dienstag, den 31.03.2020, 11:56 +0200 schrieb Daniel:
>>> Wouldn't that cause headaches when opening the document on another
>>> computer? Or what is a session?
>>
>> Depends on the workflow. If several
On 2020-03-31 12:40, Jürgen Spitzmüller wrote:
Am Dienstag, den 31.03.2020, 11:56 +0200 schrieb Daniel:
Wouldn't that cause headaches when opening the document on another
computer? Or what is a session?
Depends on the workflow. If several people work on a document, it might
make sense that
Am Dienstag, den 31.03.2020, 11:56 +0200 schrieb Daniel:
> Wouldn't that cause headaches when opening the document on another
> computer? Or what is a session?
Depends on the workflow. If several people work on a document, it might
make sense that inset states remain as the individual users set
On 2020-03-31 08:01, Jürgen Spitzmüller wrote:
Am Montag, den 30.03.2020, 21:14 +0200 schrieb Daniel:
Of course, this will leave unfixed the problem that by default LyX
does not saved inset states.
LyX does save inset states. What it does not do is render the document
dirty if an inset state
Am Montag, den 30.03.2020, 21:14 +0200 schrieb Daniel:
> Of course, this will leave unfixed the problem that by default LyX
> does not saved inset states.
LyX does save inset states. What it does not do is render the document
dirty if an inset state changes. The latter would be too an
On 2020-03-30 19:12, Pavel Sanda wrote:
On Mon, Mar 30, 2020 at 07:11:01PM +0200, Jürgen Spitzmüller wrote:
I think that's all overkill. If we push my patch, Daniel can customize
his preferred behavior and we others can all keep ours.
I tend to agree with this. Pavel
Of course, this will
On Mon, Mar 30, 2020 at 07:11:01PM +0200, Jürgen Spitzmüller wrote:
> I think that's all overkill. If we push my patch, Daniel can customize
> his preferred behavior and we others can all keep ours.
I tend to agree with this. Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
Am Montag, den 30.03.2020, 19:01 +0200 schrieb Pavel Sanda:
> We already have 'Save transient properties' concept, so this
> could be part of it or just another checkbox if ppl thing this
> is important.
> The document would be set dirty when this option would be on &
> yo
Am Mon, 30 Mar 2020 19:01:58 +0200
schrieb Pavel Sanda :
> On Mon, Mar 30, 2020 at 06:43:35PM +0200, Daniel wrote:
> > The only alternative, I can think of is enabling Save when an inset is
> > changed but don't render the document dirty. But that doesn't seem
> > completel
On Mon, Mar 30, 2020 at 06:43:35PM +0200, Daniel wrote:
> The only alternative, I can think of is enabling Save when an inset is
> changed but don't render the document dirty. But that doesn't seem
> completely different only more narrow.
>
> What did you have in mind?
We alr
solution is quite different, I'll just add reversal of this
change to my private patchset ;)
But the point of my message was to point out that there is also price
for the proposed change namely for the use cases where people rely on
timestamps as its encouranges useless save. Whether we want to pay
Am Montag, den 30.03.2020, 16:46 +0200 schrieb Daniel:
> Alternatively, as mentioned that Libre provides a special Save
> button symbol rather than disabled. Would that help,
Not me.
> or is it disabling in particular that is needed?
Yes.
Jürgen
signature.asc
De
I'll just add reversal of this
change to my private patchset ;)
But the point of my message was to point out that there is also price
for the proposed change namely for the use cases where people rely on
timestamps as its encouranges useless save. Whether we want to pay it
or no depends on wh
On 2020-03-30 14:24, Pavel Sanda wrote:
On Mon, Mar 30, 2020 at 08:46:26AM +0200, Daniel wrote:
What is lost if forced save is the default?
It depends how exactly it is done. If the icon for save/menu does not look
disabled
after save, I will tend to press it just "for sure".
On Mon, Mar 30, 2020 at 08:46:26AM +0200, Daniel wrote:
> What is lost if forced save is the default?
It depends how exactly it is done. If the icon for save/menu does not look
disabled
after save, I will tend to press it just "for sure". This gives the file new
timestamp an
-the-save-button-2016-edition/
http://document-foundation-mail-archive.969070.n3.nabble.com/Minutes-of-the-Design-Hangout-2015-12-11-td4169745.html
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Montag, den 30.03.2020, 11:35 +0200 schrieb Daniel:
> The forced save I had in mind would still not save when the buffer
> is
> read only. The "ReadOnly" argument takes care of that, right?
Sure. This only circumvents the "has unsaved changes" test.
Jürge
On 2020-03-29 16:23, Jürgen Spitzmüller wrote:
Any objections to the patch attached?
Jürgen
The forced save I had in mind would still not save when the buffer is
read only. The "ReadOnly" argument takes care of that, right?
Daniel
--
lyx-devel mailing list
lyx-devel@lists.ly
of them (F2) for "buffer-write force"?
Jürgen
I guess it would also need an additional menu entry as well in order for
people to get to know about shortcut and make easily use of it.
However, a "Save Force" entry or function isn't really something people
are f
Am Sonntag, den 29.03.2020, 16:56 +0200 schrieb Kornel Benko:
> Clever (the patch), keeping old behaviour and at the same time
> allowing a new shortcut.
Since we have two shortcuts for buffer-write (at least in cua and mac
bind), how about using one of them (F2) for "buffer-write force"?
Jürgen
On 3/29/20 10:56 AM, Kornel Benko wrote:
> Am Sun, 29 Mar 2020 16:40:51 +0200
> schrieb Jürgen Spitzmüller :
>
>> Am Sonntag, den 29.03.2020, 16:35 +0200 schrieb Jean-Marc Lasgouttes:
>>> I would even not object to a patch that saves unconditionally. We
>>> could
>>> think afterwards about
Am Sonntag, den 29.03.2020, 16:56 +0200 schrieb Kornel Benko:
> Clever (the patch), keeping old behaviour and at the same time
> allowing a new shortcut.
Yes, that's the idea :-)
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
Am Sun, 29 Mar 2020 16:40:51 +0200
schrieb Jürgen Spitzmüller :
> Am Sonntag, den 29.03.2020, 16:35 +0200 schrieb Jean-Marc Lasgouttes:
> > I would even not object to a patch that saves unconditionally. We
> > could
> > think afterwards about indicating dirty in the icon.
>
> We could do that
Am Sonntag, den 29.03.2020, 16:35 +0200 schrieb Jean-Marc Lasgouttes:
> I would even not object to a patch that saves unconditionally. We
> could
> think afterwards about indicating dirty in the icon.
We could do that on top of that, if we want.
Personally, though, I like the current behavior,
Le 29/03/2020 à 16:23, Jürgen Spitzmüller a écrit :
You mean if the document is not dirty? Hit "s", backspace, then save.
I.e, make it dirty.
Any objections to the patch attached?
I would even not object to a patch that saves unconditionally. We could
think afterwards about indica
Am Donnerstag, den 19.03.2020, 09:43 -0400 schrieb Richard Kimberly
Heck:
> 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
>
On 3/28/20 3:23 PM, racoon wrote:
> On 2020-03-28 20:16, Richard Kimberly Heck wrote:
>> On 3/28/20 3:00 PM, Richard Kimberly Heck wrote:
>>> On 3/28/20 2:55 PM, Daniel wrote:
On 2020-03-28 19:47, Richard Kimberly Heck wrote:
> On 3/28/20 5:17 AM, Daniel wrote:
>> On 2020-03-28 04:27,
On 2020-03-28 20:16, Richard Kimberly Heck wrote:
On 3/28/20 3:00 PM, Richard Kimberly Heck wrote:
On 3/28/20 2:55 PM, Daniel wrote:
On 2020-03-28 19:47, Richard Kimberly Heck wrote:
On 3/28/20 5:17 AM, Daniel wrote:
On 2020-03-28 04:27, Richard Kimberly Heck wrote:
On 3/27/20 2:48 PM,
On 3/28/20 3:00 PM, Richard Kimberly Heck wrote:
> On 3/28/20 2:55 PM, Daniel wrote:
>> On 2020-03-28 19:47, Richard Kimberly Heck wrote:
>>> On 3/28/20 5:17 AM, Daniel wrote:
On 2020-03-28 04:27, Richard Kimberly Heck wrote:
> On 3/27/20 2:48 PM, racoon wrote:
>> On 2020-03-27 19:25,
On 3/28/20 2:55 PM, Daniel wrote:
> On 2020-03-28 19:47, Richard Kimberly Heck wrote:
>> On 3/28/20 5:17 AM, Daniel wrote:
>>> On 2020-03-28 04:27, Richard Kimberly Heck wrote:
On 3/27/20 2:48 PM, racoon wrote:
> On 2020-03-27 19:25, Richard Kimberly Heck wrote:
>> On 3/27/20 2:21 PM,
On 2020-03-28 19:47, Richard Kimberly Heck wrote:
On 3/28/20 5:17 AM, Daniel wrote:
On 2020-03-28 04:27, Richard Kimberly Heck wrote:
On 3/27/20 2:48 PM, racoon wrote:
On 2020-03-27 19:25, Richard Kimberly Heck wrote:
On 3/27/20 2:21 PM, racoon wrote:
On 2020-03-27 17:52, racoon wrote:
On
On 3/28/20 5:17 AM, Daniel wrote:
> On 2020-03-28 04:27, Richard Kimberly Heck wrote:
>> On 3/27/20 2:48 PM, racoon wrote:
>>> On 2020-03-27 19:25, Richard Kimberly Heck wrote:
On 3/27/20 2:21 PM, racoon wrote:
> On 2020-03-27 17:52, racoon wrote:
>> On 2020-03-27 17:41, Richard
On 2020-03-28 04:27, Richard Kimberly Heck wrote:
On 3/27/20 2:48 PM, racoon wrote:
On 2020-03-27 19:25, Richard Kimberly Heck wrote:
On 3/27/20 2:21 PM, racoon wrote:
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
Am Freitag, den 27.03.2020, 14:25 -0400 schrieb Richard Kimberly Heck:
> Try adding "escape" first. That clears the selection. Of course, you
> lose the selection.
How about a simple buffer-mark-dirty lfun for convenience?
Jürgen
signature.asc
Description: This is a digitally signed message
On 3/27/20 2:48 PM, racoon wrote:
> On 2020-03-27 19:25, Richard Kimberly Heck wrote:
>> On 3/27/20 2:21 PM, racoon wrote:
>>> 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-27 19:25, Richard Kimberly Heck wrote:
On 3/27/20 2:21 PM, racoon wrote:
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:
On 3/27/20 2:21 PM, racoon wrote:
> 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
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;
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
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
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
and Scribus. Also, I guess it is
not a feature that would be particularly useful in office applications
only. Inkscape, for example, didn't have it either. Many applications
allow for always saving, e.g. Skim and Visual Studio Code, but don't
have toolbar icons for save at all.
Daniel
--
lyx
On Fri, Mar 20, 2020 at 07:12:00PM +0100, Daniel wrote:
> I think such an indication is optional, but might be a good idea. Except for
> libre office I saw no other application that has this indication. Maybe
> because the indication in the title is already considered sufficient?
As far as I
guess we would need some new state, which would allow icon to have
indication that save is possible but not needed.
That's at least what I see with libre office (open office I tested
here behave as nowadays lyx).
I think such an indication is optional, but might be a good idea. Except
for libre
new state, which would allow icon to have
indication that save is possible but not needed.
That's at least what I see with libre office (open office I tested
here behave as nowadays lyx).
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On 3/20/20 7:30 AM, Kornel Benko wrote:
> Am Fri, 20 Mar 2020 10:19:05 +0100
> schrieb Jean-Marc Lasgouttes :
>
>> Le 20/03/2020 à 08:11, Daniel a écrit :
>>> Save As is a bit complicated as a general replacement for Save. But I
>>> can't remember to use it
Am Fri, 20 Mar 2020 10:19:05 +0100
schrieb Jean-Marc Lasgouttes :
> Le 20/03/2020 à 08:11, Daniel a écrit :
> > Save As is a bit complicated as a general replacement for Save. But I
> > can't remember to use it just for some cases. When I make changes to
> > insets that s
Le 20/03/2020 à 08:11, Daniel a écrit :
Save As is a bit complicated as a general replacement for Save. But I
can't remember to use it just for some cases. When I make changes to
insets that seem important to me I just think I should be able to save
them as I save every other document change
On 2020-03-19 23:09, Guenter Milde wrote:
On 2020-03-19, 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
On 2020-03-19, 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,
>>>> e
On 2020-03-19 17:26, Daniel wrote:
On 2020-03-19 17:22, Jean-Marc Lasgouttes wrote:
Le 19/03/2020 à 15:14, racoon a écrit :
(For some reasons my RE posts get a "Is being held until the list
moderator can review it for approval.")
The reason is that you are not subscribed with this address. I
On 2020-03-19 17:22, Jean-Marc Lasgouttes wrote:
Le 19/03/2020 à 15:14, racoon a écrit :
(For some reasons my RE posts get a "Is being held until the list
moderator can review it for approval.")
The reason is that you are not subscribed with this address. I added the
other address to the
Le 19/03/2020 à 15:14, racoon a écrit :
(For some reasons my RE posts get a "Is being held until the list
moderator can review it for approval.")
The reason is that you are not subscribed with this address. I added the
other address to the whitelist now.
JMarc
--
lyx-devel mailing list
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
On 2020-03-19 14:53, 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
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
, 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
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,
> > >
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
> > > > > > choos
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
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 ch
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.
>
>
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
64 matches
Mail list logo
