Re: activate another split view window by shortcut

On Sun, Feb 21, 2021 at 10:22:05PM +, V K wrote: > I checked new find ??? it's much more comfortable than previous! One thing > ??? after reaching end and continuing search from beginning by Enter active > is not search area but text area, so hitting Enter deletes matched word and > creates

Re: activate another split view window by shortcut

On Sunday, February 21, 2021, 10:39:39 PM GMT+2, Pavel Sanda wrote: On Sat, Feb 20, 2021 at 03:35:04AM +, V K wrote: > P. S. I can't compile lyx master in Manjaro (Arch derivative) anymore because > of autoconf versions: > > Using autoconf (GNU Autoconf) 2.71 > This autoconf

Re: Thoughts on new split-inset feature

On Sun, Dec 27, 2020 at 02:28:52PM +0100, Jürgen Spitzmüller wrote: > Am Freitag, dem 25.12.2020 um 13:51 +0100 schrieb Jürgen Spitzmüller: > > Am Donnerstag, dem 24.12.2020 um 11:09 -0500 schrieb Scott Kostyshak: > > > 1. If I split a program listing, a bla

Re: Thoughts on new split-inset feature

Am Freitag, dem 25.12.2020 um 13:51 +0100 schrieb Jürgen Spitzmüller: > Am Donnerstag, dem 24.12.2020 um 11:09 -0500 schrieb Scott Kostyshak: > > 1. If I split a program listing, a blank line is created at the > > beginning of the second inset. I did not expect

Re: Thoughts on new split-inset feature

On Fri, Dec 25, 2020 at 01:51:02PM +0100, Jürgen Spitzmüller wrote: > Am Donnerstag, dem 24.12.2020 um 11:09 -0500 schrieb Scott Kostyshak: > > 1. If I split a program listing, a blank line is created at the > > beginning of the second inset. I did not expect this extra line. >

Re: Thoughts on new split-inset feature

Am Donnerstag, dem 24.12.2020 um 11:09 -0500 schrieb Scott Kostyshak: > 1. If I split a program listing, a blank line is created at the > beginning of the second inset. I did not expect this extra line. This is because DEPM does nothing in listings insets. Conceptually, the empty line is c

Thoughts on new split-inset feature

Thanks to Jürgen for adding this feature! (see https://www.lyx.org/trac/ticket/10260) I tested it and it works well. I have some thoughts, which are not meant specifically for Jürgen since they are more thoughts about extra functionality, not necessarily bugs. 1. If I split a program listing

Re: #10571: Tabs not showing properly in macOS full (and split) screen

13 schrieb Daniel : >>>>>>>>> >>>>>>>>> On 2020-07-30 21:21, Stephan Witt wrote: >>>>>>>>>> Am 29.07.2020 um 22:59 schrieb Daniel : >>>>>>>>>>> >>>>>>

Re: #10571: Tabs not showing properly in macOS full (and split) screen

in macOS full (and split) screen ---+- Reporter: racoon | Owner: lasgouttes Type: defect | Status: new Priority: normal | Milestone: Component: general| Version: 2.2.2 Severity: normal | Resolution

Re: #10571: Tabs not showing properly in macOS full (and split) screen

Am 04.08.2020 um 15:52 schrieb Jürgen Spitzmüller : > > Am Dienstag, den 04.08.2020, 15:42 +0200 schrieb Stephan Witt: >>> It would be good if someone on more standard linux environment like >>> GNOME/KDE >>> could test as well. >> >> >> That would be good. > > On GNOME I see no difference

Re: #10571: Tabs not showing properly in macOS full (and split) screen

0 21:21, Stephan Witt wrote: >>>>>>>>> Am 29.07.2020 um 22:59 schrieb Daniel : >>>>>>>>>> >>>>>>>>>> On 2020-07-29 21:03, Stephan Witt wrote: >>>>>>>>>>> Am 29.07.2020 um 10:15 schr

Re: #10571: Tabs not showing properly in macOS full (and split) screen

Am Dienstag, den 04.08.2020, 15:42 +0200 schrieb Stephan Witt: > > It would be good if someone on more standard linux environment like > > GNOME/KDE > > could test as well. > > > That would be good. On GNOME I see no difference between master and stable. Jürgen signature.asc Description:

Re: #10571: Tabs not showing properly in macOS full (and split) screen

Am 03.08.2020 um 23:45 schrieb Pavel Sanda : > > On Sun, Aug 02, 2020 at 10:55:55AM +0200, Stephan Witt wrote: >> Here is the current state of my patch to improve switch to/from full-screen. >> >> It contains additional code to detect switch to/from window maximize state. >> This is actually not

Re: #10571: Tabs not showing properly in macOS full (and split) screen

On Sun, Aug 02, 2020 at 10:55:55AM +0200, Stephan Witt wrote: > Here is the current state of my patch to improve switch to/from full-screen. > > It contains additional code to detect switch to/from window maximize state. > This is actually not used yet. On Mac it could be a possibility to

Re: #10571: Tabs not showing properly in macOS full (and split) screen

: On 2020-07-30 21:21, Stephan Witt wrote: Am 29.07.2020 um 22:59 schrieb Daniel : On 2020-07-29 21:03, Stephan Witt wrote: Am 29.07.2020 um 10:15 schrieb LyX Ticket Tracker : #10571: Tabs not showing properly in macOS full (and split) screen

Re: #10571: Tabs not showing properly in macOS full (and split) screen

Am 02.08.2020 um 17:52 schrieb Yu Jin : > > Am So., 2. Aug. 2020 um 10:56 Uhr schrieb Stephan Witt : > Does it work as expected for you and on Linux? Can anyone test it on Windows, > please? > > I have tested on Windows. First I want to mention that your patch was > corrupted, git said "error:

Re: #10571: Tabs not showing properly in macOS full (and split) screen

itt wrote: >>>>> Am 31.07.2020 um 07:13 schrieb Daniel : >>>>>> >>>>>> On 2020-07-30 21:21, Stephan Witt wrote: >>>>>>> Am 29.07.2020 um 22:59 schrieb Daniel : >>>>>>>> >>>>>>>> On 2020-07-29 21:0

Re: #10571: Tabs not showing properly in macOS full (and split) screen

Am So., 2. Aug. 2020 um 10:56 Uhr schrieb Stephan Witt : > Does it work as expected for you and on Linux? Can anyone test it on > Windows, please? > I have tested on Windows. First I want to mention that your patch was corrupted, git said "error: corrupted patch at line 21", I had to add a

Re: #10571: Tabs not showing properly in macOS full (and split) screen

On Sun, Aug 2, 2020 at 2:56 AM Stephan Witt wrote: > > Does it work as expected for you and on Linux? Can anyone test it on > Windows, please? > I can test on Windows 10 with a 4K display, but I cannot build. If you can send an installer, I'll give it a try. Thanks, Joel -- lyx-devel mailing

Re: #10571: Tabs not showing properly in macOS full (and split) screen

: On 2020-07-29 21:03, Stephan Witt wrote: Am 29.07.2020 um 10:15 schrieb LyX Ticket Tracker : #10571: Tabs not showing properly in macOS full (and split) screen ---+- Reporter: racoon | Owner: lasgouttes Type: defect | Status

Re: #10571: Tabs not showing properly in macOS full (and split) screen

wrote: >>>>> Am 29.07.2020 um 22:59 schrieb Daniel : >>>>>> >>>>>> On 2020-07-29 21:03, Stephan Witt wrote: >>>>>>> Am 29.07.2020 um 10:15 schrieb LyX Ticket Tracker : >>>>>>>> >>>>>>>>

Re: #10571: Tabs not showing properly in macOS full (and split) screen

t;>> On 2020-07-29 21:03, Stephan Witt wrote: >>>>>> Am 29.07.2020 um 10:15 schrieb LyX Ticket Tracker : >>>>>>> >>>>>>> #10571: Tabs not showing properly in macOS full (and split) screen >>>>>>> ---

Re: #10571: Tabs not showing properly in macOS full (and split) screen

in macOS full (and split) screen ---+- Reporter: racoon | Owner: lasgouttes Type: defect | Status: new Priority: normal | Milestone: Component: general| Version: 2.2.2 Severity: normal | Resolution

Re: #10571: Tabs not showing properly in macOS full (and split) screen

t; >>>>> #10571: Tabs not showing properly in macOS full (and split) screen >>>>> ---+- >>>>> Reporter: racoon | Owner: lasgouttes >>>>> Type: defect | Status: new

Re: #10571: Tabs not showing properly in macOS full (and split) screen

On 2020-07-30 21:21, Stephan Witt wrote: Am 29.07.2020 um 22:59 schrieb Daniel : On 2020-07-29 21:03, Stephan Witt wrote: Am 29.07.2020 um 10:15 schrieb LyX Ticket Tracker : #10571: Tabs not showing properly in macOS full (and split) screen

Re: #10571: Tabs not showing properly in macOS full (and split) screen

Am 29.07.2020 um 22:59 schrieb Daniel : > > On 2020-07-29 21:03, Stephan Witt wrote: >> Am 29.07.2020 um 10:15 schrieb LyX Ticket Tracker : >>> >>> #10571: Tabs not showing properly in macOS full (and split) screen >>> ---+

Re: #10571: Tabs not showing properly in macOS full (and split) screen

Am 30.07.2020 um 16:33 schrieb Pavel Sanda : > > On Wed, Jul 29, 2020 at 09:03:27PM +0200, Stephan Witt wrote: >> The attached patch improves the situation on Mac. I???m confident that this >> is the right move. >> But I???m unable to tell if it works on other platforms or if it breaks the >>

Re: #10571: Tabs not showing properly in macOS full (and split) screen

On Wed, Jul 29, 2020 at 09:03:27PM +0200, Stephan Witt wrote: > The attached patch improves the situation on Mac. I???m confident that this > is the right move. > But I???m unable to tell if it works on other platforms or if it breaks the > current state. > > Furthermore I???m not sure what to

Re: #10571: Tabs not showing properly in macOS full (and split) screen

On 2020-07-29 21:03, Stephan Witt wrote: Am 29.07.2020 um 10:15 schrieb LyX Ticket Tracker : #10571: Tabs not showing properly in macOS full (and split) screen ---+- Reporter: racoon | Owner: lasgouttes Type: defect

Re: #10571: Tabs not showing properly in macOS full (and split) screen

Am 29.07.2020 um 10:15 schrieb LyX Ticket Tracker : > > #10571: Tabs not showing properly in macOS full (and split) screen > ---+- > Reporter: racoon | Owner: lasgouttes > Type: defect | Status: new >

Re: Crashes & selection bug in split view

Le 21/10/2018 à 09:18, Andrew Parsloe a écrit : Since updating to 2.3.1-1 (on windows 7) I am getting sporadic but recurrent crashes -- about 4 now. The message is always I do not see the crash, but I can confirm that when the workarea is split (horizontally or vertically) and one

Re: Cursor position when view is split

On 08/10/2018 22:40, Andrew Parsloe wrote: When the view is split into left and right windows, the cursor is placed at the *start* of the document in the right window. I wonder if this is the best place? Shouldn't it initially be placed at the same position as in the left pane? My pattern

Cursor position when view is split

When the view is split into left and right windows, the cursor is placed at the *start* of the document in the right window. I wonder if this is the best place? Shouldn't it initially be placed at the same position as in the left pane? My pattern of work is to start LyX, open a document

Re: [LyX/2.3.x] beamer.lyx: document the environment-split changes.

Le 03/01/2018 à 10:49, Jürgen Spitzmüller a écrit : Am Mittwoch, den 03.01.2018, 10:14 +0100 schrieb Jean-Pierre Chrétien: * here I have no shortcut defined for 'environment-split', so the keyword 'indéfini' appears with the French interface in all localized beamer.lyx files. Should

Re: [LyX/2.3.x] beamer.lyx: document the environment-split changes.

t defined for 'environment-split', so the > keyword > 'indéfini' appears with the French interface in all localized > beamer.lyx files. > Should not this shortcut come with LyX code? I looked for the string > in the LyX > code, I find it nowhere but in a LFUN definition (I do not find at > a

Re: [LyX/2.3.x] beamer.lyx: document the environment-split changes.

; Date: Mon Jan 1 12:36:44 2018 +0100 > > > > beamer.lyx: document the environment-split changes. > > Dear Developers > > First of all, I wish you all and your families a happy New Year. > Keep up the good work in 2018! > > Referring to the subject, I ha

Re: [LyX/2.3.x] beamer.lyx: document the environment-split changes.

Le 01/01/2018 à 12:47, Juergen Spitzmueller a écrit : commit c3779cec2dd7ec198b2d409f59b438f94203746c Author: Juergen Spitzmueller <sp...@lyx.org> Date: Mon Jan 1 12:36:44 2018 +0100 beamer.lyx: document the environment-split changes. Dear Developers First of all, I wish y

Re: [LyX/master] Split external_templates to individual *.xtemplate files

Am Sonntag, 26. März 2017 um 15:34:03, schrieb Juergen Spitzmueller <sp...@lyx.org> > commit 52019917f411c72ffa6fd8200bc5a89d286d87be > Author: Juergen Spitzmueller <sp...@lyx.org> > Date: Sun Mar 26 15:32:01 2017 +0200 > > Split external_templates to i

Re: [LyX/2.2.2-staging] Fix display of InsetCollapsable with split views

> commit 6a1803e18dfac1720920a4fc8c500300658bc7d7 Author: Jean-Marc Lasgouttes <lasgout...@lyx.org> Date: Wed Feb 3 10:37:29 2016 +0100 Fix display of InsetCollapsable with split views May I ask why this (and other) commit goes to 2.2.2-staging? When will it make into 2.3-staging? I thought,

LyX/2.2.2-staging Discussion [Was: Fix display of InsetCollapsable with split views]

On 04/19/2016 05:41 PM, Scott Kostyshak wrote: > On Tue, Apr 19, 2016 at 11:19:15PM +0200, Kornel Benko wrote: >> Am Dienstag, 19. April 2016 um 17:01:58, schrieb Richard Heck >> >>> >>> Note that nothing goes to 2.2.x-staging that is not in 2.3-staging. This >>> is the same as

Re: [LyX/2.2.2-staging] Fix display of InsetCollapsable with split views

4fc8c500300658bc7d7 > > >>>> Author: Jean-Marc Lasgouttes <lasgout...@lyx.org> > > >>>> Date: Wed Feb 3 10:37:29 2016 +0100 > > >>>> > > >>>> Fix display of InsetCollapsable with split views > > >>>

Re: [LyX/2.2.2-staging] Fix display of InsetCollapsable with split views

enko a écrit : > >>> Am Dienstag, 19. April 2016 um 12:04:19, schrieb Jean-Marc Lasgouttes > >>> <lasgout...@lyx.org> > >>>> commit 6a1803e18dfac1720920a4fc8c500300658bc7d7 > >>>> Author: Jean-Marc Lasgouttes <lasgout...@lyx.org> >

Re: [LyX/2.2.2-staging] Fix display of InsetCollapsable with split views

gt; <lasgout...@lyx.org> >>>> commit 6a1803e18dfac1720920a4fc8c500300658bc7d7 >>>> Author: Jean-Marc Lasgouttes <lasgout...@lyx.org> >>>> Date: Wed Feb 3 10:37:29 2016 +0100 >>>> >>>> Fix display of InsetCollapsable with

Re: [LyX/2.2.2-staging] Fix display of InsetCollapsable with split views

03e18dfac1720920a4fc8c500300658bc7d7 > >> Author: Jean-Marc Lasgouttes <lasgout...@lyx.org> > >> Date: Wed Feb 3 10:37:29 2016 +0100 > >> > >> Fix display of InsetCollapsable with split views > > > > May I ask why this (and other) commit goes to

Re: [LyX/2.2.2-staging] Fix display of InsetCollapsable with split views

Fix display of InsetCollapsable with split views May I ask why this (and other) commit goes to 2.2.2-staging? When will it make into 2.3-staging? I thought, that new things go first to later versions and will eventually be backported. I put it there yesterday at b31a9937d. JMarc

Re: [LyX/2.2.2-staging] Fix display of InsetCollapsable with split views

Am Dienstag, 19. April 2016 um 12:04:19, schrieb Jean-Marc Lasgouttes <lasgout...@lyx.org> > commit 6a1803e18dfac1720920a4fc8c500300658bc7d7 > Author: Jean-Marc Lasgouttes <lasgout...@lyx.org> > Date: Wed Feb 3 10:37:29 2016 +0100 > > Fix display of InsetCollapsa

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

On Thu, Feb 19, 2015 at 10:54 PM, James koopsm...@gmail.com wrote: Scott I've created a ticket. I just added most of the description from the mailing list thread and then attached the documents I created to recreate the problem. cheers James Great! Thanks a lot for taking the time to

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

On Wed, Feb 18, 2015 at 10:38 AM, Richard Heck rgh...@lyx.org wrote: On 02/18/2015 12:26 AM, Scott Kostyshak wrote: On Wed, Feb 18, 2015 at 12:21 AM, James koopsm...@gmail.com wrote: I had difficulties attaching the files to the email because the thales.memphis.edu. host server kept

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

On Wed, Feb 18, 2015 at 10:38 AM, Richard Heck wrote: > On 02/18/2015 12:26 AM, Scott Kostyshak wrote: >> >> On Wed, Feb 18, 2015 at 12:21 AM, James wrote: >> >>> I had difficulties attaching the files to the email because the >>> thales.memphis.edu. >>> host

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

On Thu, Feb 19, 2015 at 10:54 PM, James wrote: > Scott > > I've created a ticket. I just added most of the description from the mailing > list thread and then attached the documents I created to recreate the > problem. > > cheers > James Great! Thanks a lot for taking the

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

On 02/18/2015 12:26 AM, Scott Kostyshak wrote: On Wed, Feb 18, 2015 at 12:21 AM, James koopsm...@gmail.com wrote: I had difficulties attaching the files to the email because the thales.memphis.edu. host server kept rejecting them on the ground of prohibited content. They were just two zipped

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

On 02/18/2015 12:26 AM, Scott Kostyshak wrote: On Wed, Feb 18, 2015 at 12:21 AM, James wrote: I had difficulties attaching the files to the email because the thales.memphis.edu. host server kept rejecting them on the ground of "prohibited content". They were just two

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

On Wed, Feb 18, 2015 at 12:21 AM, James koopsm...@gmail.com wrote: I had difficulties attaching the files to the email because the thales.memphis.edu. host server kept rejecting them on the ground of prohibited content. They were just two zipped files with LyX files in them. Instead I have

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

the buffers on one side of the split screen. A second use of ' buffer-forall buffer-close' caused a different crash - SIGSEGV signal caught (see attached image). The two other documents I tested each have 10 child documents within the master. One was an Article (standard class), the other

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

Hi James, Thanks for the report. On Tue, Feb 17, 2015 at 3:05 AM, James koopsm...@gmail.com wrote: Trying to use the Close All function when the screen is split into multiple windows often leads to LyX becoming unresponsive (i.e. Windows not responding message). The program doesn't recover

Close All used with split view crashes LyX 2.1.2 and 2.1.3

Trying to use the Close All function when the screen is split into multiple windows often leads to LyX becoming unresponsive (i.e. Windows not responding message). The program doesn't recover even when left for hours. It seems to happen when there are several child documents of a large master

Close All used with split view crashes LyX 2.1.2 and 2.1.3

Trying to use the "Close All" function when the screen is split into multiple windows often leads to LyX becoming unresponsive (i.e. Windows "not responding" message). The program doesn't recover even when left for hours. It seems to happen when there are several child documen

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

Hi James, Thanks for the report. On Tue, Feb 17, 2015 at 3:05 AM, James <koopsm...@gmail.com> wrote: > Trying to use the "Close All" function when the screen is split into > multiple windows often leads to LyX becoming unresponsive (i.e. Windows "not > responding&

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

problem with that command? > Using the mini buffer commands only closed the buffers on one side of the split screen. A second use of ' buffer-forall buffer-close' caused a different crash - SIGSEGV signal caught (see attached image). The two other documents I tested each have 10 child document

Re: Close All used with split view crashes LyX 2.1.2 and 2.1.3

On Wed, Feb 18, 2015 at 12:21 AM, James wrote: > I had difficulties attaching the files to the email because the > thales.memphis.edu. > host server kept rejecting them on the ground of "prohibited content". > They were just two zipped files with LyX files in them. > Instead

Re: Cursor movement bug in math insets with split views

As a matter of interest, is Instant Preview on in Tools Preferences Display? If I turn it off, the problem vanishes. Andrew I will need to have a look. I have did quite some work in this area to check whether the instant preview is shown in the correct view, whether the inset is being

Re: Cursor movement bug in math insets with split views

On 11/04/2014 7:11 p.m., Vincent van Ravesteijn wrote: As a matter of interest, is Instant Preview on in Tools Preferences Display? If I turn it off, the problem vanishes. Andrew I will need to have a look. I have did quite some work in this area to check whether the instant preview is

Re: Cursor movement bug in math insets with split views

On Fri, Apr 11, 2014 at 11:30 AM, aparsloe apars...@clear.net.nz wrote: On 11/04/2014 7:11 p.m., Vincent van Ravesteijn wrote: As a matter of interest, is Instant Preview on in Tools Preferences Display? If I turn it off, the problem vanishes. Andrew I will need to have a look. I have

Re: Cursor movement bug in math insets with split views

On 04/11/2014 05:36 AM, Vincent van Ravesteijn wrote: Yes, I carefully copy-pasted the bug when I created the InsetPreview ;). Perfect! Richard

Re: Cursor movement bug in math insets with split views

> > As a matter of interest, is Instant Preview on in Tools > Preferences > > Display? If I turn it off, the problem vanishes. > > Andrew > I will need to have a look. I have did quite some work in this area to check whether the instant preview is shown in the correct view, whether the inset is

Re: Cursor movement bug in math insets with split views

On 11/04/2014 7:11 p.m., Vincent van Ravesteijn wrote: As a matter of interest, is Instant Preview on in Tools > Preferences > Display? If I turn it off, the problem vanishes. Andrew I will need to have a look. I have did quite some work in this area to check whether the instant preview is

Re: Cursor movement bug in math insets with split views

On Fri, Apr 11, 2014 at 11:30 AM, aparsloe wrote: > > On 11/04/2014 7:11 p.m., Vincent van Ravesteijn wrote: >>> >>> As a matter of interest, is Instant Preview on in Tools > Preferences > >>> Display? If I turn it off, the problem vanishes. >>> >>> Andrew >>> >> I will

Re: Cursor movement bug in math insets with split views

On 04/11/2014 05:36 AM, Vincent van Ravesteijn wrote: Yes, I carefully copy-pasted the bug when I created the InsetPreview ;). Perfect! Richard

Re: Cursor movement bug in math insets with split views

On 7/04/2014 2:21 p.m., Richard Heck wrote: On 04/06/2014 08:55 PM, aparsloe wrote: On 7/04/2014 12:47 p.m., aparsloe wrote: In a new document open a math inset and enter e=mc^2. Split the view into left and right views. In the right view ensure the cursor lies *outside* the math inset. Now

Re: Cursor movement bug in math insets with split views

On 7/04/2014 2:21 p.m., Richard Heck wrote: On 04/06/2014 08:55 PM, aparsloe wrote: On 7/04/2014 12:47 p.m., aparsloe wrote: In a new document open a math inset and enter e=mc^2. Split the view into left and right views. In the right view ensure the cursor lies *outside* the math inset. Now

Re: Cursor movement bug in math insets with split views

On 7/04/2014 2:21 p.m., Richard Heck wrote: On 04/06/2014 08:55 PM, aparsloe wrote: On 7/04/2014 12:47 p.m., aparsloe wrote: In a new document open a math inset and enter e=mc^2. Split the view into left and right views. In the right view ensure the cursor lies *outside* the math inset. Now

Re: Cursor movement bug in math insets with split views

On 7/04/2014 2:21 p.m., Richard Heck wrote: On 04/06/2014 08:55 PM, aparsloe wrote: On 7/04/2014 12:47 p.m., aparsloe wrote: In a new document open a math inset and enter e=mc^2. Split the view into left and right views. In the right view ensure the cursor lies *outside* the math inset. Now

Cursor movement bug in math insets with split views

In a new document open a math inset and enter e=mc^2. Split the view into left and right views. In the right view ensure the cursor lies *outside* the math inset. Now in the left view try to put the cursor *with the mouse* between, say, m and c. I find the cursor remains stuck at the start

Re: Cursor movement bug in math insets with split views

On 7/04/2014 12:47 p.m., aparsloe wrote: In a new document open a math inset and enter e=mc^2. Split the view into left and right views. In the right view ensure the cursor lies *outside* the math inset. Now in the left view try to put the cursor *with the mouse* between, say, m and c. I find

Re: Cursor movement bug in math insets with split views

On 04/06/2014 08:55 PM, aparsloe wrote: On 7/04/2014 12:47 p.m., aparsloe wrote: In a new document open a math inset and enter e=mc^2. Split the view into left and right views. In the right view ensure the cursor lies *outside* the math inset. Now in the left view try to put the cursor

Cursor movement bug in math insets with split views

In a new document open a math inset and enter e=mc^2. Split the view into left and right views. In the right view ensure the cursor lies *outside* the math inset. Now in the left view try to put the cursor *with the mouse* between, say, "m" and "c". I find the cursor remains

Re: Cursor movement bug in math insets with split views

On 7/04/2014 12:47 p.m., aparsloe wrote: In a new document open a math inset and enter e=mc^2. Split the view into left and right views. In the right view ensure the cursor lies *outside* the math inset. Now in the left view try to put the cursor *with the mouse* between, say, "m"

Re: Cursor movement bug in math insets with split views

On 04/06/2014 08:55 PM, aparsloe wrote: On 7/04/2014 12:47 p.m., aparsloe wrote: In a new document open a math inset and enter e=mc^2. Split the view into left and right views. In the right view ensure the cursor lies *outside* the math inset. Now in the left view try to put the cursor

Re: [LyX features/kill-tex2lyx-define] Split the encoding stuff and move the static helper methods to the new class BufferEncodings.

...@lyx.org Date: Fri Aug 23 07:46:35 2013 +0200 Split the encoding stuff and move the static helper methods to the new class BufferEncodings. --- Summary of changes: configure.ac |2 +- src

Re: [LyX features/kill-tex2lyx-define] Split the encoding stuff and move the static helper methods to the new class BufferEncodings.

: The branch, kill-tex2lyx-define, has been updated. - Log - commit ed55131e8a83bfa9c70dcb89b4e836f3af546d52 Author: Stephan Witt sw...@lyx.org Date: Fri Aug 23 07:46:35 2013 +0200 Split the encoding stuff

Re: [LyX features/kill-tex2lyx-define] Split the encoding stuff and move the static helper methods to the new class BufferEncodings.

23 07:46:35 2013 +0200 Split the encoding stuff and move the static helper methods to the new class BufferEncodings. --- Summary of changes: configure.ac |2 +- src/Buffer.cpp

Re: [LyX features/kill-tex2lyx-define] Split the encoding stuff and move the static helper methods to the new class BufferEncodings.

836f3af546d52 > Author: Stephan Witt <sw...@lyx.org> > Date: Fri Aug 23 07:46:35 2013 +0200 > >Split the encoding stuff and move the static helper methods to the new > class BufferEncodings. >

Re: [LyX features/kill-tex2lyx-define] Split the encoding stuff and move the static helper methods to the new class BufferEncodings.

f546d52 > > Author: Stephan Witt <sw...@lyx.org> > > Date: Fri Aug 23 07:46:35 2013 +0200 > > > >Split the encoding stuff and move the static helper methods to the new > > class BufferEncodings. > > > ---

Re: [LyX features/kill-tex2lyx-define] Split the encoding stuff and move the static helper methods to the new class BufferEncodings.

> > - Log - > > > > > > commit ed55131e8a83bfa9c70dcb89b4e836f3af546d52 > > > Author: Stephan Witt <sw.

Re: [LyX features/kill-tex2lyx-define] Split the encoding stuff and move the static helper methods to the new class BufferEncodings.

Estamos encerrados para férias de 1 a 29 de Agosto. Regressamos no dia 30 de Agosto, por favor entre em contato connosco a partir dessa data. Out of the office from the 1st to the 29th of August Com os melhores cumprimentos / kind regards A Diretora / The directors Idalina Meireles / Sofia

Re: [LyX features/kill-tex2lyx-define] Split the encoding stuff and move the static helper methods to the new class BufferEncodings.

Estamos encerrados para férias de 1 a 29 de Agosto. Regressamos no dia 30 de Agosto, por favor entre em contato connosco a partir dessa data. Out of the office from the 1st to the 29th of August Com os melhores cumprimentos / kind regards A Diretora / The directors Idalina Meireles / Sofia

Re: [LyX master] Split the overcrowded and chaotic UI pref pane into two (#7524)

Juergen Spitzmueller wrote: commit a4a610221ae62897b792ef2e5fb9bb6f65e7b1df Author: Juergen Spitzmueller sp...@lyx.org Date: Sat Mar 2 12:24:32 2013 +0100 Split the overcrowded and chaotic UI pref pane into two (#7524) nice nice nice

Re: [LyX master] Split the overcrowded and chaotic UI pref pane into two (#7524)

Juergen Spitzmueller wrote: > commit a4a610221ae62897b792ef2e5fb9bb6f65e7b1df > Author: Juergen Spitzmueller <sp...@lyx.org> > Date: Sat Mar 2 12:24:32 2013 +0100 > > Split the overcrowded and chaotic UI pref pane into two (#7524) nice nice nice

Re: Re: [LyX master] Split roundtrip tests (at least on cmake build) to show better grained output

Am Sonntag, 30. Dezember 2012 um 15:25:26, schrieb José Matos jama...@lyx.org On 12/30/2012 10:29 AM, Kornel Benko wrote: I am not a python expert. If it does not harm, we may omit 'close_fds=True'. It still works on UNIX, so I will remove it. Vincent Kornel

Re: Re: [LyX master] Split roundtrip tests (at least on cmake build) to show better grained output

Am Sonntag, 30. Dezember 2012 um 15:25:26, schrieb José Matos > On 12/30/2012 10:29 AM, Kornel Benko wrote: > > > > I am not a python expert. If it does not harm, we may omit > > 'close_fds=True'. > > > > It still works on UNIX, so I will remove it. > > > > > > > > > Vincent >

Re: [LyX master] Split roundtrip tests (at least on cmake build) to show better grained output

Op 14-12-2012 19:08, Kornel Benko schreef: The branch, master, has been updated. - Log - commit 2b66f1b1aca8661d9aca0adca1f5db769c8dc9eb Author: Kornel Benko kor...@lyx.org Date: Fri Dec 14 19:07:28 2012 +0100 Split

Re: Re: [LyX master] Split roundtrip tests (at least on cmake build) to show better grained output

2b66f1b1aca8661d9aca0adca1f5db769c8dc9eb Author: Kornel Benko kor...@lyx.org Date: Fri Dec 14 19:07:28 2012 +0100 Split roundtrip tests (at least on cmake build) to show better grained output @@ -59,7 +62,17 @@ def main(argv): else: lyxfile = os.path.join(outputdir, base + .lyx

Re: [LyX master] Split roundtrip tests (at least on cmake build) to show better grained output

On 12/30/2012 10:29 AM, Kornel Benko wrote: I am not a python expert. If it does not harm, we may omit 'close_fds=True'. It still works on UNIX, so I will remove it. Vincent Kornel The funny part is that this would help on Windows since on Unix we can have more files opened

Re: [LyX master] Split roundtrip tests (at least on cmake build) to show better grained output

Op 14-12-2012 19:08, Kornel Benko schreef: The branch, master, has been updated. - Log - commit 2b66f1b1aca8661d9aca0adca1f5db769c8dc9eb Author: Kornel Benko <kor...@lyx.org> Date: Fri Dec 14 19:07:28 2012 +0100

Re: Re: [LyX master] Split roundtrip tests (at least on cmake build) to show better grained output

> > > > commit 2b66f1b1aca8661d9aca0adca1f5db769c8dc9eb > > Author: Kornel Benko <kor...@lyx.org> > > Date: Fri Dec 14 19:07:28 2012 +0100 > > > > Split roundtrip tests (at least on cmake build) > > to show better grained output > > >

Re: [LyX master] Split roundtrip tests (at least on cmake build) to show better grained output

On 12/30/2012 10:29 AM, Kornel Benko wrote: > > I am not a python expert. If it does not harm, we may omit > 'close_fds=True'. > > It still works on UNIX, so I will remove it. > > > > > Vincent > > > > > > > Kornel > The funny part is that this would help on Windows since on Unix we can have

Left-click problems with split views

This is in LyX 2.0.4 on Windows Vista. Open a document with a float: Figure or wrap: Figure inset (or table wrap float). Split the view -- left/right or upper/lower doesn't matter. In the new view the inset will open or close with a left click (the cursor turns from the text I-shape

Left-click problems with split views

This is in LyX 2.0.4 on Windows Vista. Open a document with a float: Figure or wrap: Figure inset (or table wrap float). Split the view -- left/right or upper/lower doesn't matter. In the new view the inset will open or close with a left click (the cursor turns from the text I-shape

Re: Closing split views from the right click menu

On 15/07/2012 2:18 p.m., Richard Heck wrote: On 07/14/2012 07:08 PM, Andrew Parsloe wrote: I'm constantly working with a split window, generally left and right views. Closing one of these views to get a single main window again means going to the View menu and clicking on Close Current View

Re: Closing split views from the right click menu

On 15/07/2012 2:18 p.m., Richard Heck wrote: On 07/14/2012 07:08 PM, Andrew Parsloe wrote: I'm constantly working with a split window, generally left and right views. Closing one of these views to get a single main window again means going to the View menu and clicking on Close Current View

  1   2   3   4   >