export tests: move hu/Tutorial_pdf5 from ignored to inverted

Dear Testers, looking at the permanently ignored tests, I see besides an obsolete style file the hungarian Tutorial - ignored with LuaTeX. As I just tried to fix a bug with Hungarian language and LuaTeX, I could not resist to try the document "by hand": Without change to the document (default

Re: make lyxdist giving me an error

On Thu, Nov 5, 2015 at 9:57 AM, Scott Kostyshak wrote: > I have been reading up on the release process at various sources, > including http://wiki.lyx.org/Devel/ReleaseProcedure. > > The following command > ./autogen.sh && ./configure --enable-build-type=pre && make lyxdist >

Re: make lyxdist giving me an error

On Thu, Nov 5, 2015 at 10:31 AM, Vincent van Ravesteijn wrote: > On Thu, Nov 5, 2015 at 9:57 AM, Scott Kostyshak wrote: >> I have been reading up on the release process at various sources, >> including http://wiki.lyx.org/Devel/ReleaseProcedure. >> >> The

make lyxdist giving me an error

I have been reading up on the release process at various sources, including http://wiki.lyx.org/Devel/ReleaseProcedure. The following command ./autogen.sh && ./configure --enable-build-type=pre && make lyxdist gives me an error: make[3]: *** No rule to make target 'test/test-insets-basic.lyx',

Re: export tests: move hu/Tutorial_pdf5 from ignored to inverted

Am Donnerstag, 5. November 2015 um 08:45:58, schrieb Guenter Milde > Dear Testers, > > looking at the permanently ignored tests, I see besides an obsolete style > file the hungarian Tutorial - ignored with LuaTeX. > > As I just tried to fix a bug with Hungarian language and

Re: export tests: move hu/Tutorial_pdf5 from ignored to inverted

Am Donnerstag, 5. November 2015 um 10:48:39, schrieb Kornel Benko > Am Donnerstag, 5. November 2015 um 08:45:58, schrieb Guenter Milde > > > Dear Testers, > > > > looking at the permanently ignored tests, I see besides an obsolete style > > file the

Re: new patch for Xe/LuaTeX with TeX-fonts

Am Mittwoch, 4. November 2015 um 22:02:52, schrieb Guenter Milde > Dear LyX developers, > > the patch below solves some of the unresolved FIXMES in the > "Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems" > 1523fc6023440f10ca0/lyxgit > > Testing shows, that this

Re: status update on the export tests

Dear Kornel, thank you for the explanation. I come a bit nearer to a generic understanding now. On 2015-11-05, Kornel Benko wrote: > Am Donnerstag, 5. November 2015 um 07:34:47, schrieb Guenter Milde > > ... >> > It is suspended _only_ if you select testcases with the '-L'

Re: status update on the export tests

Am Donnerstag, 5. November 2015 um 12:43:12, schrieb Guenter Milde > Dear Kornel, > > thank you for the explanation. I come a bit nearer to a generic > understanding now. > > On 2015-11-05, Kornel Benko wrote: > > Am Donnerstag, 5. November 2015 um 07:34:47, schrieb Guenter

Re: export tests: move hu/Tutorial_pdf5 from ignored to inverted

Am Donnerstag, 5. November 2015 um 11:00:37, schrieb Kornel Benko > > > With changed preamble (use non-TeX fonts + fixing the fragile user > > > preamble > > > (removing the loading of lmodern.sty)), both XeLaTeX and LuaLaTeX exports > > > work fine! > > > > > > So, no reason

Re: status update on the export tests

Am Donnerstag, 5. November 2015 um 07:34:47, schrieb Guenter Milde ... > > It is suspended _only_ if you select testcases with the '-L' parameter. > > OK. My idea was that suspended testcases are skipped by default. Let me sketch our use of '-L' parameter. This should

UserGuide.lyx on BibLaTeX (?)

Hey guys, Now that the use of biblatex and loading of its bibliography databases has been simplified by the introduction of BIBINPUTS, I was wondering if you'd be interested in including a few words about it in the User Guide. Something along these lines, perhaps: 6.5.3 Bibliography

Re: screen indenting after frames

On 05 Nov 2015, at 18:27, Jürgen Spitzmüller wrote: > Am Mittwoch 04 November 2015, 10:28:38 schrieb Edwin Leuven: >> atm when using beamer the text is indented after a new frame: >> >> Frame [title] >> >> ->|Text starts here >> >> and with a fragile frame it is indented

Re: status update on the export tests

On 2015-11-05, Kornel Benko wrote: > Am Donnerstag, 5. November 2015 um 12:43:12, schrieb Guenter Milde > ... >> > (from here on it matches revertedTests) >> iv. Prepend INVERTED... to testname. Revert test verification. >> > Now calling ctest with '-L export' selects

[ALPHA] Re: Two Shortcut Changes

On 11/04/2015 11:33 AM, Richard Heck wrote: Attached are two patches inspired by bug #9830. The request there was to make master-buffer-view and master-buffer-update fall back to buffer-view and buffer-update, since it's annoying to have to use different shortcuts with different documents,

Re: status update on the export tests

Am Donnerstag, 5. November 2015 um 16:56:32, schrieb Guenter Milde > On 2015-11-05, Kornel Benko wrote: > > Am Donnerstag, 5. November 2015 um 12:43:12, schrieb Guenter Milde > > > ... > > No, the tests do not have any special naming. As they are a

Re: screen indenting after frames

Am Mittwoch 04 November 2015, 10:28:38 schrieb Edwin Leuven: > dear all, > > atm when using beamer the text is indented after a new frame: > > Frame [title] > > ->|Text starts here > > and with a fragile frame it is indented even more > > Frame (fragile) [title] > >

Re: Two Shortcut Changes

On 11/05/2015 01:28 AM, Pavel Sanda wrote: Richard Heck wrote: The second patch addresses a related but different issue. In cua.bind, C-S-T is bound to "buffer-update ps" and C-S-D to "buffer-update dvi". It seems to me that it would be good to have one of these bound to "buffer-update pdf"

Re: Two Shortcut Changes

Richard Heck wrote: > C-R is bound to buffer-view. What this gets you depends upon the default > output format. So in some (many?) cases this would be PDF, but not all. So Well, that's what I meant. If you get default install there is no more shortcut to postscript, while two shortcut to pdf,

Re: UserGuide.lyx on BibLaTeX (?)

These are good suggestions. What I'd suggest is that you prepare a patch with these changes made *and with change tracking activated*. On 11/05/2015 11:01 AM, PhilipPirrip wrote: Hey guys, Now that the use of biblatex and loading of its bibliography databases has been simplified by the

Re: [ALPHA] Re: Two Shortcut Changes

On Thu, Nov 05, 2015 at 12:10:30PM -0500, Richard Heck wrote: > On 11/04/2015 11:33 AM, Richard Heck wrote: > > > >Attached are two patches inspired by bug #9830. The request there was to > >make master-buffer-view and master-buffer-update fall back to buffer-view > >and buffer-update, since it's

Re: Unit testing

On 03/11/2015 14:28, Jean-Marc Lasgouttes wrote: Le 02/11/2015 21:36, Vincent van Ravesteijn a écrit : Dear all, I have prepared a unit test framework based on google-test (gtest). You can see the commits at http://git.lyx.org/?p=developers/vfr/lyx.git;a=shortlog;h=refs/heads/tests. It

[patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

Dear all, I started to work on bug 9744 in order tor get better test results, as discussed. Attached is a proof of concept for the automatic font selection. The GUI logic is partly wrong, and the fonts are not yet stored independently, but apart from that it should work. However, while

Re: Unit testing

On 04/11/2015 14:30, Vincent van Ravesteijn wrote: However, I would also count as advantage, if there is someone familiar with the framework and willing to do the setup and lend a helping hand to others. (Maybe, the toolkit with the most developers willing to work on should win.) We have

Re: new patch for Xe/LuaTeX with TeX-fonts

On 2015-11-05, Kornel Benko wrote: > Am Mittwoch, 4. November 2015 um 22:02:52, schrieb Guenter Milde > >> the patch below solves some of the unresolved FIXMES in the >> "Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems" >> 1523fc6023440f10ca0/lyxgit >> Testing

Re: UserGuide.lyx on BibLaTeX (?)

On 11/05/2015 01:14 PM, Richard Heck wrote: These are good suggestions. What I'd suggest is that you prepare a patch with these changes made *and with change tracking activated*. Thanks, Richard. Attaching the patch. On 11/05/2015 11:01 AM, PhilipPirrip wrote: Hey guys, Now that the

Re: Two Shortcut Changes

On 6/11/2015 6:33 a.m., Pavel Sanda wrote: Richard Heck wrote: C-R is bound to buffer-view. What this gets you depends upon the default output format. So in some (many?) cases this would be PDF, but not all. So Well, that's what I meant. If you get default install there is no more shortcut

Re: Two Shortcut Changes

Le 05/11/15 21:34, Richard Heck a écrit : I've used PSTricks extensively with LyX. Having a shortcut to ps output has been very convenient. This seems like a case where you should set the default output format to Postscript, no? I'd say the same. I am not sure what the use case is, except

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Vincent van Ravesteijn wrote: > I think that a regular use-case is that one author writes, and the other > one provides feedback using track changes. Yes, I did not think of that (because I prefer giving feedback on paper, and if I receive feedback then mostly from people who do not use LyX...)

Re: Two Shortcut Changes

On 11/05/2015 03:29 PM, Andrew Parsloe wrote: On 6/11/2015 6:33 a.m., Pavel Sanda wrote: Richard Heck wrote: C-R is bound to buffer-view. What this gets you depends upon the default output format. So in some (many?) cases this would be PDF, but not all. So Well, that's what I meant. If you

Re: [ALPHA] Change Toggling Bug

On 11/05/2015 04:02 PM, Jean-Marc Lasgouttes wrote: Le 05/11/15 21:41, Richard Heck a écrit : Trivial fix: > case LFUN_CHANGES_TRACK: > buffer_.params().track_changes = > !buffer_.params().track_changes; > + buffer().markDirty(); Va de retro, satanas!

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > Le 04/11/2015 20:06, Georg Baum a écrit : > > My experience with multi-author collaboration and change tracking > differs. The various portions of the document tend to "belong" to one > author and an author uses change tracking depending on whether that part > belongs to

Re: [LyX/master] Document the export tests and other tests

Guenter Milde wrote: > Agreed. OTOH, I would prefer to have tests separated from src/, so maybe > > lib/ > src/ > tests/ > unittests/ > export-tests/ > functional/ > tests-scripts > input/ > expected/ # expected output > output/ # just a dir for the output, no content

Re: [ALPHA] Change Toggling Bug

Le 05/11/15 21:41, Richard Heck a écrit : Trivial fix: > case LFUN_CHANGES_TRACK: > buffer_.params().track_changes = > !buffer_.params().track_changes; > + buffer().markDirty(); Va de retro, satanas! Never ever call marDirty explicitly! Trivial fix is

Re: [ALPHA] Change Toggling Bug

On 11/05/2015 04:02 PM, Jean-Marc Lasgouttes wrote: Le 05/11/15 21:41, Richard Heck a écrit : Trivial fix: > case LFUN_CHANGES_TRACK: > buffer_.params().track_changes = > !buffer_.params().track_changes; > + buffer().markDirty(); Va de retro, satanas!

[ALPHA] Change Toggling Bug

On 11/05/2015 03:29 PM, Georg Baum wrote: Vincent van Ravesteijn wrote: Toggling track_changes does not even mark the document as changed, so you cannot save it. So, when I'm ready writing and I want my collaborator to use track changes, I'll have turn on track changes, make a change, undo

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > express any intention. Your description gives the impression that if > your collaborator starts writing and they do not see that the changes > are not being tracked, then they will not know or care about enabling > change tracking, as if they had no clue, and this little

Re: [ALPHA] Change Toggling Bug

Op 5 nov. 2015 22:44 schreef "Richard Heck" : > > On 11/05/2015 04:02 PM, Jean-Marc Lasgouttes wrote: >> >> Le 05/11/15 21:41, Richard Heck a écrit : >>> >>> Trivial fix: >> >> >> > case LFUN_CHANGES_TRACK: >> > buffer_.params().track_changes = >> >

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > So we tend to switch change tracking many times. Would be distinguishing between CT-on 'permanent' vs 'this session only' (automatically discarded when file is closed) of any help? Pavel

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > That "CT lock" feature, instead of imposing such a strict constraint > (that could always be circumvented one way or the other...), could maybe > display instead a message like "Pavel Sanda has requested that changes > be tracked. Are you sure that you want to disable

Re: [patch] Finding the generated latex file

Le 04/11/2015 17:16, PhilipPirrip a écrit : I personally find this very annoying. As a user. It doesn't happen on Linux, so I'm still good, but on Windows: I tested the patch on Windows, no messages were shown if LyX was closed, Windows Explorer window would just close upon the deletion of the

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

On Fri, Nov 06, 2015 at 01:41:22AM +, Guillaume Munch wrote: > >I think there is general consensus about \justification and \output_changes, > >so if this is OK with Scott you could move these to preferences, but for > >\track_changes I do not see a consensus, so this setting should not be >

Re: [patch] Finding the generated latex file

On 6/11/2015 3:32 p.m., Guillaume Munch wrote: Le 04/11/2015 17:16, PhilipPirrip a écrit : I personally find this very annoying. As a user. It doesn't happen on Linux, so I'm still good, but on Windows: I tested the patch on Windows, no messages were shown if LyX was closed, Windows Explorer

Re: [patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

On Thu, Nov 05, 2015 at 09:12:56PM +0100, Georg Baum wrote: > The test problem could easily be solved in the test machinery instead: When > exporting via XeTeX or LuaTeX, switch to non-TeX fonts, even if the document > has a different setting. Unless someone presents a convincing use case for

Re: [patch] Finding the generated latex file

On Fri, Nov 06, 2015 at 02:32:13AM +, Guillaume Munch wrote: > Le 04/11/2015 17:16, PhilipPirrip a écrit : > > > >I personally find this very annoying. As a user. It doesn't happen on > >Linux, so I'm still good, but on Windows: > >I tested the patch on Windows, no messages were shown if LyX

Re: [patch] Finding the generated latex file

Le 06/11/2015 03:16, Scott Kostyshak a écrit : On Fri, Nov 06, 2015 at 02:32:13AM +, Guillaume Munch wrote: Le 04/11/2015 17:16, PhilipPirrip a écrit : I personally find this very annoying. As a user. It doesn't happen on Linux, so I'm still good, but on Windows: I tested the patch on

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Le 05/11/2015 07:31, Vincent van Ravesteijn a écrit : On Thu, Nov 5, 2015 at 7:12 AM, Pavel Sanda wrote: Vincent van Ravesteijn wrote: I consider it also document, not user, setting. It would cause confusions if this setting is not transfered to my collaborators within the

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Le 05/11/2015 20:25, Georg Baum a écrit : Guillaume Munch wrote: Le 04/11/2015 20:06, Georg Baum a écrit : My experience with multi-author collaboration and change tracking differs. The various portions of the document tend to "belong" to one author and an author uses change tracking

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Vincent van Ravesteijn wrote: > What actually makes sense is to have a document setting like > "under_version_control". When the user opens such a document (for the first > time?) we turn on change tracking. Not sure I am following what you propose. under_version_control is related to our VCS

Re: screen indenting after frames

Am Donnerstag 05 November 2015, 18:57:52 schrieb Edwin Leuven: > i agree > > may i suggest that you push this change to master? I've pushed something similar. Might be something to consider for branch. Jürgen > thanks, edwin

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Op 6 nov. 2015 05:44 schreef "Pavel Sanda" : > > Guillaume Munch wrote: > > That "CT lock" feature, instead of imposing such a strict constraint > > (that could always be circumvented one way or the other...), could maybe > > display instead a message like "Pavel Sanda has requested