Re: Enhancement Idea: Combination Horizontal and Vertical Split Screen in Lyx

On Wed, Nov 27, 2024 at 09:32:39PM -0500, Louis Hiener wrote: > Hi Scott, > > Thanks for replying so quickly! > > Taking your points/questions in reverse order: For my use case, one > scenario would be to be able to split the main window vertically (into left > and right halves) with the split be

Re: Enhancement Idea: Combination Horizontal and Vertical Split Screen in Lyx

Hi Pavel, Thank you for replying so quickly! I like your work-around. It will certainly help in the short term, and may be sufficient for the long term as well. I'll give it a try! Kind regards, Lou On Tue, Nov 19, 2024 at 5:23 AM Pavel Sanda wrote: > On Mon, Nov 18, 2024 at 09:37:45PM -0500,

Re: Enhancement Idea: Combination Horizontal and Vertical Split Screen in Lyx

Hi Scott, Thanks for replying so quickly! Taking your points/questions in reverse order: For my use case, one scenario would be to be able to split the main window vertically (into left and right halves) with the split being adjustable as it is in Lyx now when you select View|Split View Into Left

Re: Enhancement Idea: Combination Horizontal and Vertical Split Screen in Lyx

On Mon, Nov 18, 2024 at 09:37:45PM -0500, Louis Hiener wrote: > Good afternoon, > > I am an embedded systems and signal processing development engineer, > and have been using Lyx in my daily work since 2001. I use it both for > capturing my daily notes (technical and otherwise), as well as for > d

Re: Enhancement Idea: Combination Horizontal and Vertical Split Screen in Lyx

On Tue, Nov 19, 2024 at 11:48:37AM +0100, Jürgen Spitzmüller wrote: > Am Dienstag, dem 19.11.2024 um 09:46 +0100 schrieb Scott Kostyshak: > > That said, it is the first time I have heard of this request from a > > user, so I don't know if developers will place it as a high priority. > > Well, we h

Re: Enhancement Idea: Combination Horizontal and Vertical Split Screen in Lyx

Am Dienstag, dem 19.11.2024 um 09:46 +0100 schrieb Scott Kostyshak: > That said, it is the first time I have heard of this request from a > user, so I don't know if developers will place it as a high priority. Well, we have a 16 year old ticket requesting this: https://www.lyx.org/trac/ticket/5044

Re: Enhancement Idea: Combination Horizontal and Vertical Split Screen in Lyx

On Mon, Nov 18, 2024 at 09:37:45PM -0500, Louis Hiener wrote: > split it in the same direction. What would be very useful (to me, at least) > would be the ability to split each split screen pane in either direction. I have work-around in case you don't know it yet. You can open the document, then

Enhancement Idea: Combination Horizontal and Vertical Split Screen in Lyx

Good afternoon, I am an embedded systems and signal processing development engineer, and have been using Lyx in my daily work since 2001. I use it both for capturing my daily notes (technical and otherwise), as well as for developing technical documentation. As average screen size has increased,

Re: Proposal for UI enhancement: ticket #1624

Am Di., 1. Okt. 2019 um 19:55 Uhr schrieb Richard Kimberly Heck < rikih...@lyx.org>: > I do still have some worries of the sort I expressed at > https://www.lyx.org/trac/ticket/1624#comment:11. A label for a section > really shouldn't be in the section heading itself, from a LaTeX point of > view,

Re: Proposal for UI enhancement: ticket #1624

Hi Riki, thanks for the ideas - quite a few things I haven't really thought about. Am 01.10.19 um 19:54 schrieb Richard Kimberly Heck: > > ... > > I do still have some worries of the sort I expressed at > https://www.lyx.org/trac/ticket/1624#comment:11. A label for a section > really shouldn't be

Re: Proposal for UI enhancement: ticket #1624

Sorry to top post, but since this isn't a response to anything particular I do still have some worries of the sort I expressed at https://www.lyx.org/trac/ticket/1624#comment:11. A label for a section really shouldn't be in the section heading itself, from a LaTeX point of view, though it's

Re: Proposal for UI enhancement: ticket #1624

On Sun, Sep 29, 2019 at 01:34:14PM +0200, Andreas Nicolai wrote: > Hi Scott, > > thanks for your ideas, let me comment below. > >> I would like to contribute an improvement on this workflow: > > >> 1. Button and sub-dialog approach: > >> - add a button on the dialog "Create label" > >> - sub-dial

Re: Proposal for UI enhancement: ticket #1624

Hi Scott, thanks for your ideas, let me comment below. >> I would like to contribute an improvement on this workflow: >> 1. Button and sub-dialog approach: >> - add a button on the dialog "Create label" >> - sub-dialog opens and allows selecting existing >> sections/subections/images/tables in a

Re: Proposal for UI enhancement: ticket #1624

On Tue, Sep 24, 2019 at 04:19:48PM +0200, Andreas Nicolai wrote: > Hi and hello everyone, > > first of all, I'm a great fan of Lyx and I use it for my productive work > since many years! Thanks for all the work you've put into. Hi Andreas, thanks for all of the time you've put thinking about this

Proposal for UI enhancement: ticket #1624

Hi and hello everyone, first of all, I'm a great fan of Lyx and I use it for my productive work since many years! Thanks for all the work you've put into. One feature I am missing for some time already is discussed in ticket https://www.lyx.org/trac/ticket/1624 It is about streamlining the "cros

Re: Fwd: #11620: Enhancement Request: Add abbreviated git hash to Insert -> Field -> Other... -> VCI

Le 11 août 2019 19:04:12 GMT+02:00, Joel Kulesza a écrit : > Happy to, I just didn't want to get ahead of myself in case this isn't > adopted in 2.4. > >This has been incorporated into the master branch. What is the path to >know if/when it will be incorporated into a forthcoming (2.4) release?

Fwd: #11620: Enhancement Request: Add abbreviated git hash to Insert -> Field -> Other... -> VCI

-- Forwarded message - From: LyX Ticket Tracker Date: Sun, Jul 28, 2019 at 7:42 PM Subject: Re: #11620: Enhancement Request: Add abbreviated git hash to Insert -> Field -> Other... -> VCI To: , Cc: #11620: Enhancement Request: Add abbreviated git hash to Insert

Re: [enhancement] add *.xlsx to external data material dialog (table) and file handler

Richard Heck wrote: > On 09/06/2016 06:10 PM, Georg Baum wrote: >> Richard Heck wrote: >> >>> On 09/05/2016 04:56 PM, Georg Baum wrote: I think he meant the missing .xlsx extension in the external material file dialog. I added this in master at df8e0ed9e0c37ab7. >>> Fine for stable too.

RE: [enhancement] add *.xlsx to external data material dialog (table) and file handler

s wider than the page). Do you have an xlsx file that ssconvert handles, but LyX does not? If so, please send me such a file so I can look into it. Helge Hafting _____ Thanks. What I am suggesting is an enhancement of lyx' ssconvert interface (i.e. for external material/tables)

Re: [enhancement] add *.xlsx to external data material dialog (table) and file handler

On 09/06/2016 06:10 PM, Georg Baum wrote: > Richard Heck wrote: > >> On 09/05/2016 04:56 PM, Georg Baum wrote: >>> I think he meant the missing .xlsx extension in the external material >>> file dialog. I added this in master at df8e0ed9e0c37ab7. >> Fine for stable too. > I need 646d47ae9393bc for s

Re: [enhancement] add *.xlsx to external data material dialog (table) and file handler

Richard Heck wrote: > On 09/05/2016 04:56 PM, Georg Baum wrote: >> I think he meant the missing .xlsx extension in the external material >> file dialog. I added this in master at df8e0ed9e0c37ab7. > > Fine for stable too. I need 646d47ae9393bc for stable too, otherwise I only see one filter "All

Re: [enhancement] add *.xlsx to external data material dialog (table) and file handler

On 09/05/2016 04:56 PM, Georg Baum wrote: > Helge Hafting wrote: > >> Den 05. sep. 2016 00:53, skrev Jannick: >>> Currently lyx deals with *.xls files only, while the Excel world rather >>> turns around .xlsx files. It would be great if lyx could be extended >>> including the file handler where ssc

Re: [enhancement] add *.xlsx to external data material dialog (table) and file handler

Helge Hafting wrote: > Den 05. sep. 2016 00:53, skrev Jannick: >> Currently lyx deals with *.xls files only, while the Excel world rather >> turns around .xlsx files. It would be great if lyx could be extended >> including the file handler where ssconvert appears to faithfully extract >> data from

Re: [enhancement] add *.xlsx to external data material dialog (table) and file handler

Den 05. sep. 2016 00:53, skrev Jannick: Currently lyx deals with *.xls files only, while the Excel world rather turns around .xlsx files. It would be great if lyx could be extended including the file handler where ssconvert appears to faithfully extract data from *.xlsx files. I am not subscri

[enhancement] add *.xlsx to external data material dialog (table) and file handler

Currently lyx deals with *.xls files only, while the Excel world rather turns around .xlsx files. It would be great if lyx could be extended including the file handler where ssconvert appears to faithfully extract data from *.xlsx files. I am not subscribed to the devel list, so please copy me in

Re: Enhancement Suggestion: Preamble Fixed-width Font

Am 15.04.2016 um 11:06 schrieb Scott Kostyshak : > > On Fri, Apr 15, 2016 at 10:36:59AM +0200, Stephan Witt wrote: >> Am 15.04.2016 um 09:51 schrieb Scott Kostyshak : >>> >>> On Thu, Apr 14, 2016 at 08:53:24PM +0200, Stephan Witt wrote: Am 14.04.2016 um 20:16 schrieb Guillaume Munch : >

Re: Enhancement Suggestion: Preamble Fixed-width Font

On Fri, Apr 15, 2016 at 10:36:59AM +0200, Stephan Witt wrote: > Am 15.04.2016 um 09:51 schrieb Scott Kostyshak : > > > > On Thu, Apr 14, 2016 at 08:53:24PM +0200, Stephan Witt wrote: > >> Am 14.04.2016 um 20:16 schrieb Guillaume Munch : > >>> > >>> Le 14/04/2016 19:05, Stephan Witt a écrit : > >>

Re: Enhancement Suggestion: Preamble Fixed-width Font

On 15/04/2016 7:51 p.m., Scott Kostyshak wrote: On Thu, Apr 14, 2016 at 08:53:24PM +0200, Stephan Witt wrote: Am 14.04.2016 um 20:16 schrieb Guillaume Munch : Le 14/04/2016 19:05, Stephan Witt a écrit : Yes, it’s attached. Thanks for testing. Works well on Linux+qt{4,5}. Two remarks: * is

Re: Enhancement Suggestion: Preamble Fixed-width Font

On Thu, Apr 14, 2016 at 08:53:24PM +0200, Stephan Witt wrote: > Am 14.04.2016 um 20:16 schrieb Guillaume Munch : > > > > Le 14/04/2016 19:05, Stephan Witt a écrit : > >> > >> Yes, it’s attached. Thanks for testing. > >> > > > > > > Works well on Linux+qt{4,5}. > > > > Two remarks: > > > > *

Re: Enhancement Suggestion: Preamble Fixed-width Font

Le 14/04/2016 19:53, Stephan Witt a écrit : Am 14.04.2016 um 20:16 schrieb Guillaume Munch : Le 14/04/2016 19:05, Stephan Witt a écrit : Yes, it’s attached. Thanks for testing. Works well on Linux+qt{4,5}. Two remarks: * isFixedPitch() would be in an anonymous namespace by what I know o

Re: Enhancement Suggestion: Preamble Fixed-width Font

Am 14.04.2016 um 20:16 schrieb Guillaume Munch : > > Le 14/04/2016 19:05, Stephan Witt a écrit : >> >> Yes, it’s attached. Thanks for testing. >> > > > Works well on Linux+qt{4,5}. > > Two remarks: > > * isFixedPitch() would be in an anonymous namespace by what I know of LyX's > code style.

Re: Enhancement Suggestion: Preamble Fixed-width Font

Le 14/04/2016 19:05, Stephan Witt a écrit : Yes, it’s attached. Thanks for testing. Works well on Linux+qt{4,5}. Two remarks: * isFixedPitch() would be in an anonymous namespace by what I know of LyX's code style. * In my patch I compute typewriterFontName() from typewriterSystemFont. Wo

Re: Enhancement Suggestion: Preamble Fixed-width Font

Am 14.04.2016 um 19:46 schrieb Guillaume Munch : > > Le 14/04/2016 18:41, Stephan Witt a écrit : >> Am 14.04.2016 um 19:28 schrieb Guillaume Munch : >>> >>> Le 14/04/2016 18:10, Stephan Witt a écrit : Am 14.04.2016 um 18:18 schrieb Joel Kulesza : > > On Thu, Apr 14, 2016 at 10:

Re: Enhancement Suggestion: Preamble Fixed-width Font

Le 14/04/2016 18:41, Stephan Witt a écrit : Am 14.04.2016 um 19:28 schrieb Guillaume Munch : Le 14/04/2016 18:10, Stephan Witt a écrit : Am 14.04.2016 um 18:18 schrieb Joel Kulesza : On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch wrote: Can you please try the attached patch? That patch

Re: Enhancement Suggestion: Preamble Fixed-width Font

Am 14.04.2016 um 19:28 schrieb Guillaume Munch : > > Le 14/04/2016 18:10, Stephan Witt a écrit : >> Am 14.04.2016 um 18:18 schrieb Joel Kulesza : >>> >>> On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch >>> wrote: >>> >>> Can you please try the attached patch? >>> >>> That patch seemed to wor

Re: Enhancement Suggestion: Preamble Fixed-width Font

Le 14/04/2016 18:10, Stephan Witt a écrit : Am 14.04.2016 um 18:18 schrieb Joel Kulesza : On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch wrote: Can you please try the attached patch? That patch seemed to work to correct the issue in both places (see attached). The font seems small (I'm no

Re: Enhancement Suggestion: Preamble Fixed-width Font

Am 14.04.2016 um 18:18 schrieb Joel Kulesza : > > On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch wrote: > > Can you please try the attached patch? > > That patch seemed to work to correct the issue in both places (see attached). > The font seems small (I'm not sure if that's perception or r

Re: Enhancement Suggestion: Preamble Fixed-width Font

Le 14/04/2016 17:18, Joel Kulesza a écrit : On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch mailto:g...@lyx.org>> wrote: Can you please try the attached patch? That patch seemed to work to correct the issue in both places (see attached). The font seems small (I'm not sure if that's perc

Re: Enhancement Suggestion: Preamble Fixed-width Font

Le 14/04/2016 13:33, Joel Kulesza a écrit : On Thu, Apr 14, 2016 at 8:29 AM, Joel Kulesza mailto:jkule...@gmail.com>> wrote: On Thu, Apr 14, 2016 at 8:18 AM, Guillaume Munch mailto:g...@lyx.org>> wrote: Yes it's there. Code is very now similar to the source panel. What font

Re: Enhancement Suggestion: Preamble Fixed-width Font

Le 14/04/2016 12:13, Joel Kulesza a écrit : On Wed, Feb 17, 2016 at 10:39 PM, Scott Kostyshak mailto:skost...@lyx.org>> wrote: On Wed, Feb 17, 2016 at 10:11:27PM -0500, Richard Heck wrote: > Seems to me a change better for 2.2.0, if Scott is all right with it. Yes go ahead. And thank

Re: Enhancement Suggestion: Preamble Fixed-width Font

On Wed, Feb 17, 2016 at 10:39 PM, Scott Kostyshak wrote: > On Wed, Feb 17, 2016 at 10:11:27PM -0500, Richard Heck wrote: > > Seems to me a change better for 2.2.0, if Scott is all right with it. > Yes go ahead. And thanks for the patch. > Scott > Is this a feature that would have been included i

Re: Enhancement Suggestion: Preamble Fixed-width Font

On Wed, Feb 17, 2016 at 10:11:27PM -0500, Richard Heck wrote: > On 02/17/2016 09:09 PM, Guillaume Munch wrote: > > Le 18/02/2016 01:58, Richard Heck a écrit : > >> On 02/17/2016 05:11 PM, Pavel Sanda wrote: > >>> Guillaume Munch wrote: > The attached patch copies code from the source panel, so

Re: Enhancement Suggestion: Preamble Fixed-width Font

On 02/17/2016 09:09 PM, Guillaume Munch wrote: > Le 18/02/2016 01:58, Richard Heck a écrit : >> On 02/17/2016 05:11 PM, Pavel Sanda wrote: >>> Guillaume Munch wrote: The attached patch copies code from the source panel, so it is safe. >>> I don't know what is the current beta policy, if Scott

Re: Enhancement Suggestion: Preamble Fixed-width Font

Le 18/02/2016 01:58, Richard Heck a écrit : On 02/17/2016 05:11 PM, Pavel Sanda wrote: Guillaume Munch wrote: The attached patch copies code from the source panel, so it is safe. I don't know what is the current beta policy, if Scott is fine with that it has my +1. Tested? If so, has my +1,

Re: Enhancement Suggestion: Preamble Fixed-width Font

On 02/17/2016 05:11 PM, Pavel Sanda wrote: > Guillaume Munch wrote: >> The attached patch copies code from the source panel, so it is safe. > I don't know what is the current beta policy, if Scott is fine with that it > has my +1. Tested? If so, has my +1, too. (No time myself right now.) rh

Re: Enhancement Suggestion: Preamble Fixed-width Font

Guillaume Munch wrote: > The attached patch copies code from the source panel, so it is safe. I don't know what is the current beta policy, if Scott is fine with that it has my +1. Pavel

Re: Enhancement Suggestion: Preamble Fixed-width Font

On 2016-02-17, Guillaume Munch wrote: > [-- Type: text/plain, Encoding: 8bit --] > Le 17/02/2016 19:10, Pavel Sanda a écrit : >> Joel Kulesza wrote: >>> My suggestion is to change the default font of the Settings->Preamble text >>> box to a fixed-width font because the content is effectively code

Re: Enhancement Suggestion: Preamble Fixed-width Font

Le 17/02/2016 19:10, Pavel Sanda a écrit : Joel Kulesza wrote: My suggestion is to change the default font of the Settings->Preamble text box to a fixed-width font because the content is effectively code. This change should improve readability for those that make extensive use of the preamble.

Re: Enhancement Suggestion: Preamble Fixed-width Font

Joel Kulesza wrote: > My suggestion is to change the default font of the Settings->Preamble text > box to a fixed-width font because the content is effectively code. This > change should improve readability for those that make extensive use of the > preamble. > > Going a step further with the top

Enhancement Suggestion: Preamble Fixed-width Font

LyX Developers, I recently submitted an enhancement request through the bug tracker and it was suggested I post here to initiate discussion on it. The TRAC ticket number is #9966 <http://www.lyx.org/trac/ticket/9966>. My suggestion is to change the default font of the Settings->Prea

Re: Corkboard/Non-linear workflow enhancement?

On Tue, Oct 21, 2014 at 5:02 AM, Ketil Thorgersen wrote: > Scott Kostyshak lyx.org> writes: > >> >> On Mon, Oct 20, 2014 at 9:43 AM, Ketil Thorgersen rytmisk.net> > wrote: >> > Hi >> > >> > I have eagerly been awaiting the development of the Corboard module for Lyx >> > outlined here: http://wik

Re: Corkboard/Non-linear workflow enhancement?

Scott Kostyshak lyx.org> writes: > > On Mon, Oct 20, 2014 at 9:43 AM, Ketil Thorgersen rytmisk.net> wrote: > > Hi > > > > I have eagerly been awaiting the development of the Corboard module for Lyx > > outlined here: http://wiki.lyx.org/GSoC/NonLinearWriting in 2013 as a > > continuation of wha

Re: Corkboard/Non-linear workflow enhancement?

On Mon, Oct 20, 2014 at 9:43 AM, Ketil Thorgersen wrote: > Hi > > I have eagerly been awaiting the development of the Corboard module for Lyx > outlined here: http://wiki.lyx.org/GSoC/NonLinearWriting in 2013 as a > continuation of what Rob Oakes developed as Lyx-outline. I used to be using > Lyx-

Corkboard/Non-linear workflow enhancement?

Hi I have eagerly been awaiting the development of the Corboard module for Lyx outlined here: http://wiki.lyx.org/GSoC/NonLinearWriting in 2013 as a continuation of what Rob Oakes developed as Lyx-outline. I used to be using Lyx-outline but then this Google summer code project came up and everyth

Re: Copier enquiry/enhancement

On 9/07/2014 12:36 a.m., Richard Heck wrote: On 07/08/2014 02:09 AM, aparsloe wrote: Is there a reason why the copier ext_copy.py in the LyX 2.1.0/Resources/scripts folder does NOT have an option for copying to the same directory as the LyX file? At present the copied files end up in a subdi

Re: Copier enquiry/enhancement

On 07/08/2014 02:09 AM, aparsloe wrote: Is there a reason why the copier ext_copy.py in the LyX 2.1.0/Resources/scripts folder does NOT have an option for copying to the same directory as the LyX file? At present the copied files end up in a subdirectory of the directory containing the LyX fil

Copier enquiry/enhancement

Is there a reason why the copier ext_copy.py in the LyX 2.1.0/Resources/scripts folder does NOT have an option for copying to the same directory as the LyX file? At present the copied files end up in a subdirectory of the directory containing the LyX file. I have a use case where copying to t

Enhancement request: parent-child relations among preview insets

Suppose you have a preview inset wrapped around some latex that gives a value to a control sequence, call it \foo. If you put \foo in ERT later in the text and wrap a preview inset around that, the value of \foo is not shown until the buffer is reloaded (when *every* preview inset is re-evaluat

Re: Re: enhancement request: support biblatex

José Matos wrote: > On Monday 28 April 2014 08:13:49 Neal Becker wrote: >> https://bugzilla.redhat.com/show_bug.cgi?id=584063 >> >> Seems fedora is not shipping biber, it is still an open bug > > Why don't you install the package from the copr repository pointed there? > > With some feedback it

Re: Re: enhancement request: support biblatex

On Monday 28 April 2014 08:13:49 Neal Becker wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=584063 > > Seems fedora is not shipping biber, it is still an open bug Why don't you install the package from the copr repository pointed there? With some feedback it will possible to place this pac

Re: enhancement request: support biblatex

On 04/28/2014 08:37 AM, stefano franchi wrote: On Mon, Apr 28, 2014 at 7:13 AM, Neal Becker > wrote: https://bugzilla.redhat.com/show_bug.cgi?id=584063 Seems fedora is not shipping biber, it is still an open bug You can always install it from their sit

Re: enhancement request: support biblatex

On Mon, Apr 28, 2014 at 7:13 AM, Neal Becker wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=584063 > > Seems fedora is not shipping biber, it is still an open bug > > You can always install it from their site, if you are willing to bypass Fedora's package management system: http://biblatex

Re: enhancement request: support biblatex

https://bugzilla.redhat.com/show_bug.cgi?id=584063 Seems fedora is not shipping biber, it is still an open bug On Mon, Apr 28, 2014 at 8:07 AM, stefano franchi wrote: > > > > On Mon, Apr 28, 2014 at 7:02 AM, Neal Becker wrote: > >> stefano franchi wrote: >> >> > On Mon, Apr 28, 2014 at 6:29 AM

Re: enhancement request: support biblatex

On Mon, Apr 28, 2014 at 7:02 AM, Neal Becker wrote: > stefano franchi wrote: > > > On Mon, Apr 28, 2014 at 6:29 AM, Neal Becker > wrote: > > > >> I have read that biblatex is the way of the future. Unfortunately, I > >> understand > >> that lyx does not currently support biblatex. > >> > > > >

Re: enhancement request: support biblatex

stefano franchi wrote: > On Mon, Apr 28, 2014 at 6:29 AM, Neal Becker wrote: > >> I have read that biblatex is the way of the future. Unfortunately, I >> understand >> that lyx does not currently support biblatex. >> > > Lyx supports biblatex *partially*. You can use biblatex in lyx with a few

Re: enhancement request: support biblatex

On Mon, Apr 28, 2014 at 6:29 AM, Neal Becker wrote: > I have read that biblatex is the way of the future. Unfortunately, I > understand > that lyx does not currently support biblatex. > Lyx supports biblatex *partially*. You can use biblatex in lyx with a few workarounds, all detailed in the co

enhancement request: support biblatex

I have read that biblatex is the way of the future. Unfortunately, I understand that lyx does not currently support biblatex.

Re: [LyX/master] Adding wrap-around pop-up question to simple find and replace dialog (fixing enhancement request #1262).

On 23/07/13 02:01, Scott Kostyshak wrote: > Yes, this is good to see. I get the impression that many people use > Adv F&R as their main F&R, even for simple queries. This sounds good, as that was the original intention, to replace the simple F&R. This duplication of features among the 2 worlds se

Re: [LyX/master] Adding wrap-around pop-up question to simple find and replace dialog (fixing enhancement request #1262).

On Mon, Jul 22, 2013 at 8:27 PM, Tommaso Cucinotta wrote: > On 23/07/13 00:34, Scott Kostyshak wrote: >>> Right, I just fixed that as well in [b32ce2cf/lyxgit]. >> >> Works well. The cursor does blink to the beginning, but this is not >> worth fixing. > > Yeah, I noticed that, but it's something b

Re: [LyX/master] Adding wrap-around pop-up question to simple find and replace dialog (fixing enhancement request #1262).

On 23/07/13 00:34, Scott Kostyshak wrote: >> Right, I just fixed that as well in [b32ce2cf/lyxgit]. > > Works well. The cursor does blink to the beginning, but this is not > worth fixing. Yeah, I noticed that, but it's something belonging to a dimension unknown to me :-). For now, I prefer to ad

Re: [LyX/master] Adding wrap-around pop-up question to simple find and replace dialog (fixing enhancement request #1262).

On Mon, Jul 22, 2013 at 6:58 PM, Tommaso Cucinotta wrote: > On 21/07/13 19:11, Scott Kostyshak wrote: >> Thanks, Tommaso. I tested and this works very well. One minor thing >> that is inconsistent with Advanced Find is that if you search for a >> string that is nowhere in the document and you clic

Re: [LyX/master] Adding wrap-around pop-up question to simple find and replace dialog (fixing enhancement request #1262).

On 21/07/13 19:11, Scott Kostyshak wrote: > Thanks, Tommaso. I tested and this works very well. One minor thing > that is inconsistent with Advanced Find is that if you search for a > string that is nowhere in the document and you click on "yes" to the > "wrap search" dialog, Advanced Find does not

Re: [LyX/master] Adding wrap-around pop-up question to simple find and replace dialog (fixing enhancement request #1262).

On Sun, Jul 21, 2013 at 12:53 PM, Tommaso Cucinotta wrote: > commit 2a86379ea7c589a75ff84d86755d214f45748550 > Author: Tommaso Cucinotta > Date: Sun Jul 21 17:51:53 2013 +0100 > > Adding wrap-around pop-up question to simple find and replace dialog > (fixing enhance

Re: GSoC: UI Improvement and Non-Linear Writing Enhancement

Cyrille Artho wrote: > I agree that it's much better to update progress on the GSoC projects on > the wiki. First, we need the original proposal (on Melange) as a reference; Note that original proposal are not visible to non-mentors, so maybe good idea to copy&paste them into wiki. Pavel

Re: GSoC: UI Improvement and Non-Linear Writing Enhancement

Hi developers, Thank you for the help! I'm very excited to participate in the project! I will put information about my project in the wiki page soon. Ashley *Xueqing Shan* Vanderbilt University, '16 On Thu, May 30, 2013 at 3:08 AM, Vincent van Ravesteijn w

Re: GSoC: UI Improvement and Non-Linear Writing Enhancement

Op 28-5-2013 16:41, Ashley Shan schreef: Hi LyX developers, My name is Xueqing Shan, and I'm a rising sophomore in Vanderbilt University. I'm very excited to participate in Google Summer of Code with LyX this year. I write this email to briefly introduce the state of my project and our (me an

Re: GSoC: UI Improvement and Non-Linear Writing Enhancement

I agree that it's much better to update progress on the GSoC projects on the wiki. First, we need the original proposal (on Melange) as a reference; second, the wiki is more accessible than the GSoC pages (which are not public), so it is good for LyX users to see what we are working on. I'v

Re: GSoC: UI Improvement and Non-Linear Writing Enhancement

On 05/28/2013 10:41 AM, Ashley Shan wrote: Hi LyX developers, My name is Xueqing Shan, and I'm a rising sophomore in Vanderbilt University. I'm very excited to participate in Google Summer of Code with LyX this year. I write this email to briefly introduce the state of my project and our (me

GSoC: UI Improvement and Non-Linear Writing Enhancement

Hi LyX developers, My name is Xueqing Shan, and I'm a rising sophomore in Vanderbilt University. I'm very excited to participate in Google Summer of Code with LyX this year. I write this email to briefly introduce the state of my project and our (me and my mentor, Rob) plans for the project, and a

Proposal (UI enhancement) updated

Hi Rob, I further updated my proposal and incorporated the topics you suggested. I reduced the learning period from 2 full weeks to one week and a half. Could you please take a very quick look when you have time? Any feedback will be appreciated. Here is the link: https://google-melange.appspot.c

Enhancement request (maybe GSOC project): Please improve latex-lyx roundtripping

Please CC me on answers. I often collaborate with people who (still) prefer LaTeX, and also submit papers to conferences that make it easy to submit latex via style/class/sample.tex files. This makes it important to be able to work in LyX, but debug/modify in latex, then continue working in Ly

Re: enhancement suggestion: include combine class

he LaTeX for an \include'd document. This is so the titlepage would be generated as normal, etc. I'm not sure what other class options we might want to support and what to leave for inclusion in the manual preamble. I'd suggest that you add an enhancement request to trac, and perhaps

enhancement suggestion: include combine class

Dear LyX-developers, first off: thanks for a great piece of software. I have one suggestion: the combine class is very handy for having several documents in one, which is especially useful for collections of articles. The class can be found on CTAN: http://www.ctan.org/tex-archive/macros/latex/con

Re: Enhancement bugs for 2.0

On 2010-04-01, Jean-Marc Lasgouttes wrote: > Le 31/03/2010 13:07, Guenter Milde a écrit : >> I wonder if we could use utf-8 as default latex source encoding for most >> (all) languages if the locale is UTF-8. > AFAIK, UTF8 support is too weak in LaTeX right now. While it is weak in LaTeX, LyX's

Re: Enhancement bugs for 2.0

Le 30/03/2010 14:01, Jean-Marc Lasgouttes a écrit : - pass the "noae" option to Sweave to make sure it does not ruin our font settings. http://www.lyx.org/trac/ticket/6624 This one is fixed now. JMarc

Re: Enhancement bugs for 2.0

Le 31/03/2010 13:07, Guenter Milde a écrit : On 2010-03-30, Jean-Marc Lasgouttes wrote: Pavel Sanda writes: last call for 2.0 feature requests we have reported. - currently, Sweave reads the files in the encoding of the current locale. This fails as soon as the locale is UTF-8 and the do

Re: Enhancement bugs for 2.0

On 2010-03-30, Jean-Marc Lasgouttes wrote: > Pavel Sanda writes: >> last call for 2.0 feature requests we have reported. > - currently, Sweave reads the files in the encoding of the current > locale. This fails as soon as the locale is UTF-8 and the document is > 8bit (because the characters

Re: Enhancement bugs for 2.0

Jean-Marc Lasgouttes wrote: > > JMarc? btw i'm generally lost whats the sweave status. > > are there some issues you still plan to do > > or just documentation is missing now? one more thing - adding entry to newinlyx20 wiki section, so documentation is not forgotten. i would add it myself if i h

Re: Enhancement bugs for 2.0

Gregor GORJANC writes: > On 30 March 2010 14:01, Jean-Marc Lasgouttes wrote: > ... >> - find a way to read local files. If I have a >>   read.table("foo.txt") >>  in the file, it will fail because R is ran from the tmp dir. Since >>   there is no PATH-like support in R, I do not know how to solve

Re: Enhancement bugs for 2.0

Pavel Sanda writes: > Jean-Marc Lasgouttes wrote: >> I marked the bug as fixedintrunk and opened new ones for each separate >> problem. The milestone is 2.0.0 for now, but we have to discuss this. > > something to be done with these two? > http://www.lyx.org/trac/ticket/48 This one I do not know

Re: Enhancement bugs for 2.0

Hi, Please read bellow. On 30 March 2010 14:01, Jean-Marc Lasgouttes wrote: ... > - find a way to read local files. If I have a >   read.table("foo.txt") >  in the file, it will fail because R is ran from the tmp dir. Since >   there is no PATH-like support in R, I do not know how to solve the >

Re: Enhancement bugs for 2.0

Jean-Marc Lasgouttes wrote: > I marked the bug as fixedintrunk and opened new ones for each separate > problem. The milestone is 2.0.0 for now, but we have to discuss this. something to be done with these two? http://www.lyx.org/trac/ticket/48 http://www.lyx.org/trac/ticket/6137 > I have also wor

Re: Enhancement bugs for 2.0

Pavel Sanda writes: > last call for 2.0 feature requests we have reported. I am really late with this, but I am a bit overwhelmed by work and baby, > > * http://www.lyx.org/trac/ticket/4072 > Default document settings in .layout files > Personnally, I am against this feature as it is presented.

Re: Enhancement bugs for 2.0

>> * http://www.lyx.org/trac/ticket/3865 >> implement to define color definitions in document settings >> >> i guess c. Uwe? > > This issue is very complicated because we have to store all colors that the user might already > have defined previously in a document. For stability reasons of 2.0, I

Fwd: Enhancement bugs for 2.0

Vincent van Ravesteijn wrote: > I'm not sure I remember what Edwin proposed. at one point i suggested to keep only the "advanced" one you then suggested to keep the "simple" one and perhaps turn it into a search bar if i remember well the issue was mainly speed of course keeping the old one ar

Re: Enhancement bugs for 2.0

Leuven recently proposed a rework of the current simple-search dialog. Are we going to have 3 search facilities ? - simple-search dialog - advanced-search pane - simple-search bar ? I'm not sure I remember what Edwin proposed. Or, are you thinking to just replace the simple-search dialog w

Re: Enhancement bugs for 2.0

Tommaso Cucinotta wrote: > Or, are you thinking to just replace the simple-search dialog with the bar > ? yes that was the proposal. pavel

Re: Enhancement bugs for 2.0

Vincent van Ravesteijn - TNW wrote: to me it was fixed by new search pane. Vincent however have idea to convert the current simple search dialog into search bar. opinions? anybody wants to work on it? otherwise c. I've already done some work on it. I really want to have this in 2.0.0, so w

Re: Enhancement bugs for 2.0

On 03/25/2010 02:16 PM, Jürgen Spitzmüller wrote: * http://www.lyx.org/trac/ticket/6455 Multiple index UI polishment - index inset should display something besides just "Idx" - Insert>Toc menu should probably say "Index: Names" rather than just "Names". Juegen, Richard? I don't see a

RE: Enhancement bugs for 2.0

Vincent van Ravesteijn - TNW wrote: > > Did you update today ? I think they are now exactly the same. > Thank you. It is much better. Still, I would go further and get rid of the advanced tab: - At the top of the pane I would put the scope as a combo box - Then a smaller Find TextEdit - Then

  1   2   >