Re: Save on save
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-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. >> >> Try adding "escape" first. That clears the selection. Of course, you >> lose the selection. >> >> Riki > > Thanks. That works better. Yes, losing the selection isn't perfect. > > Btw. the action input field suffers from the same problem as the > shortcut editor, e.g. it masks line-breaks which make a command fail. I don't know if there is any easy solution to this. I think I'd regard it as a Qt bug. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Save on save
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: 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. Try adding "escape" first. That clears the selection. Of course, you lose the selection. Riki Thanks. That works better. Yes, losing the selection isn't perfect. Btw. the action input field suffers from the same problem as the shortcut editor, e.g. it masks line-breaks which make a command fail. Daniel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Save on save
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 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. Try adding "escape" first. That clears the selection. Of course, you lose the selection. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Registry handling on windows (installer)
Am Fr., 27. März 2020 um 19:04 Uhr schrieb Richard Kimberly Heck < rikih...@lyx.org>: > On 3/23/20 1:49 PM, Yu Jin wrote: > > Here is another patch, I updated the description of DTL update, because > the newer version does not work with miktex, as discussed on the mailing > list today. > > Can you post all the necessary patches in one message? I've gotten a bit > confused about which is which. > Ok, here they are, I put the numbers in right order for it to be more clear. Eugene 0005-imagemagick-convert-and-description.patch Description: Binary data 0001-implemented-64-bit-installer-removed-registry-hackin.patch Description: Binary data 0004-updatelog-master.patch Description: Binary data 0002-changed-main-registry-entry-LyX-Version-now-added-la.patch Description: Binary data 0006-DTL-update-is-not-usable.patch Description: Binary data 0003-description-for-windows-installer-and-dependencies.patch Description: Binary data -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Save on save
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 -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Registry handling on windows (installer)
On 3/23/20 1:49 PM, Yu Jin wrote:
> Am Fr., 20. März 2020 um 21:05 Uhr schrieb Yu Jin
> mailto:technikma...@gmail.com>>:
>
> Am Fr., 20. März 2020 um 20:16 Uhr schrieb Richard Kimberly Heck
> mailto:rikih...@lyx.org>>:
>
> I will do so by the end of the weekend. The main question is
> whether
> these will affect my 2.3.x builds in any way.
>
> You would have to change the line
>
> !insertmacro FileListMSVC File "${FILES_LYX}\bin\"
> (file "install.nsh")
>
> you need the macro FileListMinGW here.
> You would also need to update the imagemagick in your
> dependencies, replacing it with the portable version.
> The main registry entry change is meant for 2.4.0, so not
> affecting your builds.
>
> Here is another patch, I updated the description of DTL update,
> because the newer version does not work with miktex, as discussed on
> the mailing list today.
Can you post all the necessary patches in one message? I've gotten a bit
confused about which is which.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Save on save
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 -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Save on save
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 -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Save on save
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. Daniel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Assertion with BATCH_outline-beamer test
Am Thu, 26 Mar 2020 19:05:36 -0400 schrieb Scott Kostyshak : > On Thu, Mar 26, 2020 at 08:08:50PM +0100, Jean-Marc Lasgouttes wrote: > > Le 26/03/2020 à 19:35, Scott Kostyshak a écrit : > > > Note that I made a recent change in a setCursor() call in outline-down > > > so that is a good candidate. > > > > Indeed :) > > Attached is an example file. To reproduce, put the cursor in the first > position of the buffer and press + . For some reason, > outline() was changing the cursor position to 1. I'm not sure if that's > intended behavior, but in any case the assertion is fixed at a higher > level at a1169188. Yes, that's fine. > On a separate issue, there's what I think is undesired behavior in that > outline() should put the frame after the next frame. Instead, it breaks > up the second frame because it wants to put the first before > "References". I'm not sure what is ideal here though, because if you > look at the outliner, you see "frame, frame, references" so you might > expect the frame to go before references after the move. I guess there > needs to be a concept of references being nested in frame and that being > shown in the outliner. > > Scott Not nice, but OTOH easy enough to handle :) Thanks Scott. Kornel pgpQgawLaiAq5.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
