Re: Bug or feature? [Change Tracking]
Am Freitag, den 08.05.2020, 17:14 -0400 schrieb Richard Kimberly Heck: > On 5/8/20 1:54 PM, Paul A. Rubin wrote: > > > Before I file a ticket on this, I'd like to get a sense of whether > > it > > is in fact a bug v. intended behavior. > > Consider a document with an activated branch containing text that > > has > > been edited, and with change tracking turned on. The user wants to > > dissolve the branch but retain the content. If the user does this > > with > > change tracking turned on, the entire branch gets crossed out and > > the > > full contents gets reproduced, which is a bit clunky to put it > > mildly. > > If the user turns off change tracking before dissolving the branch > > inset, the branch contents are retained but none of the change > > information survives. In particular, if the user has replaced one > > word > > with another, both words will survive in the latter case. > > I tripped over this recently. My preferred behavior would be that > > (with tracking temporarily turned off) dissolving the inset would > > preserve the contents including tracking info. Am I off base here? > > > I would also think that is what should happen. A whole lot has been > done > > in master on change tracking by Jürgen, though, so this may be be > fixed. Yes: https://www.lyx.org/trac/ticket/10128 Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Bug or feature? [Change Tracking]
On 5/8/20 1:54 PM, Paul A. Rubin wrote: > Before I file a ticket on this, I'd like to get a sense of whether it > is in fact a bug v. intended behavior. > > Consider a document with an activated branch containing text that has > been edited, and with change tracking turned on. The user wants to > dissolve the branch but retain the content. If the user does this with > change tracking turned on, the entire branch gets crossed out and the > full contents gets reproduced, which is a bit clunky to put it mildly. > If the user turns off change tracking before dissolving the branch > inset, the branch contents are retained but none of the change > information survives. In particular, if the user has replaced one word > with another, both words will survive in the latter case. > > I tripped over this recently. My preferred behavior would be that > (with tracking temporarily turned off) dissolving the inset would > preserve the contents including tracking info. Am I off base here? I would also think that is what should happen. A whole lot has been done in master on change tracking by Jürgen, though, so this may be be fixed. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Bug or feature?
Before I file a ticket on this, I'd like to get a sense of whether it is in fact a bug v. intended behavior. Consider a document with an activated branch containing text that has been edited, and with change tracking turned on. The user wants to dissolve the branch but retain the content. If the user does this with change tracking turned on, the entire branch gets crossed out and the full contents gets reproduced, which is a bit clunky to put it mildly. If the user turns off change tracking before dissolving the branch inset, the branch contents are retained but none of the change information survives. In particular, if the user has replaced one word with another, both words will survive in the latter case. I tripped over this recently. My preferred behavior would be that (with tracking temporarily turned off) dissolving the inset would preserve the contents including tracking info. Am I off base here? Thanks for any feedback, Paul -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Cleaning patches
On 5/7/20 7:14 PM, Thibaut Cuvelier wrote: > Dear list, > > While working on DocBook support > (https://gitlab.com/gadmm/lyx-unstable/-/merge_requests/3), I made a > bit of clean-up, i.e. correcting one typo and updating lyx2lyx 2.4 to > respect a bit better the PEP8 (i.e. the official code conventions for > Python, https://www.python.org/dev/peps/pep-0008/). To automate PEP8 > corrections, there is already a tool that does it quite well: > https://github.com/PyCQA/pycodestyle. > > I don't know how important these issues are for LyX (I never saw the > topic being discussed), please let me know! We do try to keep the code as clean as we can. Committed! Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Paths forgotten?
Thanks, Pavel. Inserting ~ manually at the beginning of the path worked fine. In 15 years of using Linux and Windows on two partitions of the same disk I never lost anything, but I do backup anyway ;-) Yours, Udi On 5/7/20 1:44 PM, Pavel Sanda wrote: On Thu, May 07, 2020 at 01:16:56PM -0400, UD Kap wrote: David, Indeed, I use Linux for (almost) everything, but have (on the same machine) a Windows 10 partition, with its own Lyx/Latex.* I naively assumed that using the browse key in setting up an image in the Lyx presentation will insert the correct path for that image file.* As I have now discovered, the path that was inserted* was valid only for the editing session in which it was inserted.* *** Prompted by your suggestion, I replaced the beginning of the path for all the confusing files (which was pointing to the Windows partition)* by ~, and now Lyx is no longer confused. Editing the same file by alternate booting to both Windows and Linux is a brave move and I hope you do regular backups :) If by chance your Windows hibernate and you try to edit the lyx file in linux on the mounted drive meanwhile, you might end up with data loss after new reboot to windows... Anyway, if the images are stored not that far away, you can use manually inserted "../" in paths (e.g. "../../another_project/fig1.eps") so it does not depend on linux vs windows path start and work in both of them. Pavel -- Ehud Kaplan, Ph.D. Visiting Professor Dept. of Philosophy & History of Science Charles University, Prague & the National Institute of Mental Health, Topolová 748, Klecany Czechia --- Jules and Doris Stein Research to Prevent Blindness Professor Director, Center of Excellence for Computational & System Neuroscience, The Friedman Brain Institute, MSSM Director, The laboratory of Visual & Computational Neuroscience Depts. of Neuroscience, Ophthalmology, Chemical & Structural Biology Icahn school of medicine at Mount Sinai One Gustave Levy Place New York, NY, 10029 USA -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Show changes in output inside insets
When adding or deleting an inset with tracked changes, then the lyxadded and lyxdeleted commands get wrapped around the content of the inset. I think this is a relatively new feature but I can't find the fixed bug report right now. This in many circumstances fine. However, in some cases this is not desired. For example, if the argument of an inset is supposed to be a latex command, like a label only cross-reference. It would be good if one could set an inset to act in the old or new way. Otherwise, for example, copy and pasting of content with tracked changes that worked properly, will make the document stop working. And it is still quite hard to track down such errors in LyX. Daniel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
