On Thu, Apr 18, 2024 at 02:59:02PM GMT, Jean-Marc Lasgouttes wrote:
> Le 12/04/2024 à 06:07, Scott Kostyshak a écrit :
> > To reproduce:
> >
> > 1. Open the attached file.
> > 2. Put the cursor just after "testing" and before the space.
> > 3. Press
Le 12/04/2024 à 06:07, Scott Kostyshak a écrit :
To reproduce:
1. Open the attached file.
2. Put the cursor just after "testing" and before the space.
3. Press .
Result: it looks like the cursor is frozen for a second.
Similarly, if after (3) you do another quick you can see t
Le 12/04/2024 à 06:07, Scott Kostyshak a écrit :
To reproduce:
1. Open the attached file.
2. Put the cursor just after "testing" and before the space.
3. Press .
Result: it looks like the cursor is frozen for a second.
Similarly, if after (3) you do another quick you can see t
ile.
> > > 2. Put the cursor just after "testing" and before the space.
> > > 3. Press .
> > >
> > > Result: it looks like the cursor is frozen for a second.
> >
> > I do not see this.
> >
> > > Similarly, if after (3) you do
On Fri, 2024-04-12 at 10:05 +0200, Kornel Benko wrote:
> Am Fri, 12 Apr 2024 00:07:06 -0400
> schrieb Scott Kostyshak :
>
> > To reproduce:
> >
> > 1. Open the attached file.
> > 2. Put the cursor just after "testing" and before the space.
> > 3.
Am Fri, 12 Apr 2024 00:07:06 -0400
schrieb Scott Kostyshak :
> To reproduce:
>
> 1. Open the attached file.
> 2. Put the cursor just after "testing" and before the space.
> 3. Press .
>
> Result: it looks like the cursor is frozen for a second.
I do not see this.
To reproduce:
1. Open the attached file.
2. Put the cursor just after "testing" and before the space.
3. Press .
Result: it looks like the cursor is frozen for a second.
Similarly, if after (3) you do another quick you can see two
cursors painted for a split second.
Can anyone
e:
> > > >
> > > > * Should we discard them
> > > > * Handle like white space
> > > >
> > > > If using in findadv with selected 'Adhere to search string formatting
> > > > of'
> > > > they are treated as ord
On Sat, Jul 22, 2023 at 05:30:16PM +0200, Kornel Benko wrote:
> Am Sat, 22 Jul 2023 06:54:37 -0400
> schrieb Scott Kostyshak :
>
> > On Sat, Jul 22, 2023 at 11:57:58AM +0200, Kornel Benko wrote:
> > >
> > > * Should we discard them
> > > * Handle like wh
Am Sat, 22 Jul 2023 06:54:37 -0400
schrieb Scott Kostyshak :
> On Sat, Jul 22, 2023 at 11:57:58AM +0200, Kornel Benko wrote:
> >
> > * Should we discard them
> > * Handle like white space
> >
> > If using in findadv with selected 'Adhere to search string fo
On Sat, Jul 22, 2023 at 11:57:58AM +0200, Kornel Benko wrote:
>
> * Should we discard them
> * Handle like white space
>
> If using in findadv with selected 'Adhere to search string formatting of'
> they are treated as ordinary non-word chars.
> Without this option, the are
* Should we discard them
* Handle like white space
If using in findadv with selected 'Adhere to search string formatting of'
they are treated as ordinary non-word chars.
Without this option, the are discarded.
I am unsure, how to proceed. Using them as white spaces disables the specific
search
Am Mon, 17 Jul 2023 15:46:34 +0200 (CEST)
schrieb Juergen Spitzmueller :
> commit f6f936e3d049c05ad0795c32696df895d8b61313
> Author: Juergen Spitzmueller
> Date: Mon Jul 17 16:58:04 2023 +0200
>
> Support protected and thin space in simple search (#12836)
Thanks.
Le 10/06/2023 à 19:06, Daniel a écrit :
On 2023-06-07 16:16, Jean-Marc Lasgouttes wrote:
Personally, I add the space before the branch. But I can see that it
is mildly annoying.
I am probably missing something here but I don't see how that is
possible at the end of the sentence as in Scott's
.
It would be nice if I could insert a space at the beginning of an
inset.
Personally, I add the space before the branch. But I can see that it
is mildly annoying.
I am probably missing something here but I don't see how that is
possible at the end of the sentence as in Scott's examples. Wouldn't
On 2023-06-11 18:57, Richard Kimberly Heck wrote:
On 6/10/23 13:06, Daniel wrote:
On 2023-06-07 16:16, Jean-Marc Lasgouttes wrote:
Le 01/06/2023 à 17:42, Scott Kostyshak a écrit :
I come across the example in the attachment often in various forms.
It would be nice if I could insert a space
On 6/10/23 13:06, Daniel wrote:
On 2023-06-07 16:16, Jean-Marc Lasgouttes wrote:
Le 01/06/2023 à 17:42, Scott Kostyshak a écrit :
I come across the example in the attachment often in various forms.
It would be nice if I could insert a space at the beginning of an
inset.
Personally, I add
On 2023-06-07 16:16, Jean-Marc Lasgouttes wrote:
Le 01/06/2023 à 17:42, Scott Kostyshak a écrit :
I come across the example in the attachment often in various forms. It
would be nice if I could insert a space at the beginning of an inset.
Personally, I add the space before the branch. But I
Le 01/06/2023 à 17:42, Scott Kostyshak a écrit :
I come across the example in the attachment often in various forms. It would be
nice if I could insert a space at the beginning of an inset.
Personally, I add the space before the branch. But I can see that it is
mildly annoying.
JMarc
On Thu, Jun 01, 2023 at 11:54:14AM -0400, Paul A. Rubin wrote:
>
> On 6/1/23 11:42, Scott Kostyshak wrote:
> > I come across the example in the attachment often in various forms. It
> > would be nice if I could insert a space at the beginning of an inset.
> >
> &g
On 6/1/23 11:42, Scott Kostyshak wrote:
I come across the example in the attachment often in various forms. It would be
nice if I could insert a space at the beginning of an inset.
Am I missing a more natural workaround than the ones shown in the example?
Scott
Would Insert > Formatt
I come across the example in the attachment often in various forms. It would be
nice if I could insert a space at the beginning of an inset.
Am I missing a more natural workaround than the ones shown in the example?
Scott
example.lyx
Description: application/lyx
signature.asc
Description
On Wed, Feb 22, 2023 at 11:04:19AM +0100, Jean-Marc Lasgouttes wrote:
> Le 16/02/2023 à 04:40, Scott Kostyshak a écrit :
> > Another git bisect lead me here. When I open the attached file, the
> > space between the two branch insets shortens if I move the cursor.
>
> Is it
Le 16/02/2023 à 04:40, Scott Kostyshak a écrit :
Another git bisect lead me here. When I open the attached file, the
space between the two branch insets shortens if I move the cursor.
Is it better now ?
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman
Le 20/02/2023 à 17:53, Scott Kostyshak a écrit :
On Mon, Feb 20, 2023 at 05:17:32PM +0100, Jean-Marc Lasgouttes wrote:
Le 10/02/2023 à 05:24, Scott Kostyshak a écrit :
Does cursor position need to be adapted for some reason? I attach two
screenshots. "bad.png" is a screenshot with this commit,
Le 20/02/2023 à 17:53, Scott Kostyshak a écrit :
On Mon, Feb 20, 2023 at 05:17:32PM +0100, Jean-Marc Lasgouttes wrote:
Le 10/02/2023 à 05:24, Scott Kostyshak a écrit :
Does cursor position need to be adapted for some reason? I attach two
screenshots. "bad.png" is a screenshot with this commit,
On Mon, Feb 20, 2023 at 05:17:32PM +0100, Jean-Marc Lasgouttes wrote:
> Le 10/02/2023 à 05:24, Scott Kostyshak a écrit :
> > Does cursor position need to be adapted for some reason? I attach two
> > screenshots. "bad.png" is a screenshot with this commit, and "good.png"
> > is the screenshot with
Le 10/02/2023 à 05:24, Scott Kostyshak a écrit :
Does cursor position need to be adapted for some reason? I attach two
screenshots. "bad.png" is a screenshot with this commit, and "good.png"
is the screenshot with the commit before. The cursor position of
"bad.png" seems to intersect the border
te:
> > > > commit 04ece4f0d6af818b3bc572b558181b947a109580
> > > > Author: Jean-Marc Lasgouttes
> > > > Date: Sun Dec 11 20:59:43 2022 +0100
> > > >
> > > > Remove space between button and text with inlines collapsible
> > > > insets
> > >
; > > Date: Sun Dec 11 20:59:43 2022 +0100
> > >
> > > Remove space between button and text with inlines collapsible insets
> > > Typically there are two sources of spacing:
> > > * the button has two pixels added to the left and to the ri
On Mon, Feb 06, 2023 at 07:34:38PM +0100, Jean-Marc Lasgouttes wrote:
> commit 04ece4f0d6af818b3bc572b558181b947a109580
> Author: Jean-Marc Lasgouttes
> Date: Sun Dec 11 20:59:43 2022 +0100
>
> Remove space between button and text with inlines collapsible insets
>
Le 12/06/2022 à 13:07, Juergen Spitzmueller a écrit :
commit b2a7b715a2c6f0d9f26a180c15e1570308dc6d6c
Author: Daniel Ramoeller
Date: Wed Jun 8 08:20:37 2022 +0200
Make space names more standard
Fix for bug #12547.
- "Interword" becomes "Normal"
Am Wed, 11 May 2022 17:38:53 +0200
schrieb Kornel Benko :
> Am Wed, 11 May 2022 17:21:52 +0200
> schrieb Jürgen Spitzmüller :
>
> > Am Mittwoch, dem 11.05.2022 um 14:18 +0200 schrieb Kornel Benko:
> > > How to search for space like
> > > hfill, medski
Am Wed, 11 May 2022 17:21:52 +0200
schrieb Jürgen Spitzmüller :
> Am Mittwoch, dem 11.05.2022 um 14:18 +0200 schrieb Kornel Benko:
> > How to search for space like
> > hfill, medskip, thinspace, visible space, quad, ...
> > and many more with regex?
>
> I'd ex
Am Mittwoch, dem 11.05.2022 um 14:18 +0200 schrieb Kornel Benko:
> How to search for space like
> hfill, medskip, thinspace, visible space, quad, ...
> and many more with regex?
I'd expect \s covers them (except for visible space).
--
Jürgen
signature.asc
Description: This is a
Am Wed, 11 May 2022 13:23:31 +0200
schrieb Jürgen Spitzmüller :
> Am Dienstag, dem 10.05.2022 um 16:50 +0200 schrieb Kornel Benko:
> > Does it make sense to add a checkbox to advanced find GUI like
> > 'Space-type'
> > which would treat all white spaces equal?
> &
Am Dienstag, dem 10.05.2022 um 16:50 +0200 schrieb Kornel Benko:
> Does it make sense to add a checkbox to advanced find GUI like
> 'Space-type'
> which would treat all white spaces equal?
> (Anything in src/insets/InsetSpace.cpp)
Smells a bit like feature creep
Does it make sense to add a checkbox to advanced find GUI like
'Space-type'
which would treat all white spaces equal?
(Anything in src/insets/InsetSpace.cpp)
If yes, then should it could go to lyx2.5?
Kornel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org
think of any reasonable
>
> > alternative to your solution. We could presumably write \space at the end
>
> > of the previous line, but I think that would be harder to implement. The
>
> > lyx2lyx part would actually be quite simple. The changes to the parser,
> a
On Monday, December 14, 2020 7:00:39 PM WET Richard Kimberly Heck wrote:
> I hadn't considered this case. It will also occur, of course, with footnotes
> and, indeed, every kind of inset. I can't think of any reasonable
> alternative to your solution. We could presumably write \space a
dle the case of languages that don't use spaces to separate
> words?
One simple example to illustrate what I mean, even assuming that the
space is our word separator. What should be the file format of the
latex paragraph?
The most famous equation of all times is $E=mc^2.$
dle the case of languages that don't use spaces to separate
> words?
One simple example to illustrate what I mean, even assuming that the
space is our word separator. What should be the file format of the
latex paragraph?
The most famous equation of all times is $E=mc^2.$
eparate
> words?
One simple example to illustrate what I mean, even assuming that the space is
our word separator. What should be the file format of the latex paragraph?
The most famous equation of all times is $E=mc^2.$
How do we represent the space between "is" and the math inset?
Now we
gt; > > > Finally, significant EOL white space seems unidiomatic in a "source
>
> > >
>
> > > file,"
>
> > >
>
> > > > which is what a .lyx file effectively is.
>
> > > >
>
> > > > This is an expert-us
Hi Joel,
I am revisiting this because I think that of points you raise are worth of
further, although not necessarily immediate attention. :-)
On Sunday, May 31, 2020 6:30:56 PM WET Joel Kulesza wrote:
> > > Finally, significant EOL white space seems unidiomatic in a "source
Le 09/09/2020 à 13:33, Pavel Sanda a écrit :
It's definitely big improvement. I would say that 2.3 version was still better,
but I can live with the current version.
Let's keep it like that for now then.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
On Wed, Sep 09, 2020 at 11:30:25AM +0200, Jean-Marc Lasgouttes wrote:
> Le 25/08/2020 ?? 16:24, Pavel Sanda a écrit :
> >On Tue, Aug 25, 2020 at 04:23:01PM +0200, Pavel Sanda wrote:
> >>>No. Note however that is is a 1 pixel difference.
> >>
> >>On the screenshot I sent it was 3 pixels for
Le 25/08/2020 à 16:24, Pavel Sanda a écrit :
On Tue, Aug 25, 2020 at 04:23:01PM +0200, Pavel Sanda wrote:
No. Note however that is is a 1 pixel difference.
On the screenshot I sent it was 3 pixels for protected and 1 for thin.
3 pixels *difference*
Indeed, I decided at the time hat having
Le 26 août 2020 22:05:29 GMT+02:00, "José Abílio Matos" a
écrit :
>On Tuesday, 25 August 2020 18.25.58 WEST Scott Kostyshak wrote:
>> Yes another slippery slope. What's next, requiring C++20 and Qt 7 for
>2.4.0?
>>
>> Scott
>
>Actually lyx 2.4 does not requires but it correctly compiles with
On Tuesday, 25 August 2020 18.25.58 WEST Scott Kostyshak wrote:
> Yes another slippery slope. What's next, requiring C++20 and Qt 7 for 2.4.0?
>
> Scott
Actually lyx 2.4 does not requires but it correctly compiles with -std=c++20.
:-)
--
José Abílio--
lyx-devel mailing list
On Tue, Aug 25, 2020 at 06:41:50PM +0200, Jean-Marc Lasgouttes wrote:
> Le 25/08/2020 à 18:35, Scott Kostyshak a écrit :
> > This is a slippery slope [1].
>
> You mean like when we added support for C++11 and now everybody is forced to
> use it? It's a plot!
Yes another slippery slope. What's
Le 25/08/2020 à 18:35, Scott Kostyshak a écrit :
This is a slippery slope [1].
You mean like when we added support for C++11 and now everybody is
forced to use it? It's a plot!
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Tue, Aug 25, 2020 at 05:11:36PM +0200, Jean-Marc Lasgouttes wrote:
> Le 25/08/2020 à 17:08, Pavel Sanda a écrit :
> > On Tue, Aug 25, 2020 at 05:06:10PM +0200, Jean-Marc Lasgouttes wrote:
> > > > I never saw problem with solution 1, what is the drawback of it?
> > > > Maybe Scott has some
Le 25/08/2020 à 17:08, Pavel Sanda a écrit :
On Tue, Aug 25, 2020 at 05:06:10PM +0200, Jean-Marc Lasgouttes wrote:
I never saw problem with solution 1, what is the drawback of it?
Maybe Scott has some opinion.
Look closely at the selected one in my second attachment. It overflows on
the
On Tue, Aug 25, 2020 at 05:06:10PM +0200, Jean-Marc Lasgouttes wrote:
> >I never saw problem with solution 1, what is the drawback of it?
> >Maybe Scott has some opinion.
>
> Look closely at the selected one in my second attachment. It overflows on
> the right.
Sorry I was not clear. I noticed
, second protected
space.
I understand that it looks small.
Does it mean that you find the size of newer screenshots acceptable?
No. Note however that is is a 1 pixel difference.
On the screenshot I sent it was 3 pixels for protected and 1 for thin.
So we could revert to the previous situation
On Tue, Aug 25, 2020 at 04:23:01PM +0200, Pavel Sanda wrote:
> > No. Note however that is is a 1 pixel difference.
>
> On the screenshot I sent it was 3 pixels for protected and 1 for thin.
3 pixels *difference*
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
On Tue, Aug 25, 2020 at 04:12:20PM +0200, Jean-Marc Lasgouttes wrote:
> Le 25/08/2020 ?? 16:03, Pavel Sanda a écrit :
> >On Tue, Aug 25, 2020 at 03:20:55PM +0200, Jean-Marc Lasgouttes wrote:
> >>>see the screenshot in attachment. first char is thin line, second
> >&g
Le 25/08/2020 à 16:03, Pavel Sanda a écrit :
On Tue, Aug 25, 2020 at 03:20:55PM +0200, Jean-Marc Lasgouttes wrote:
see the screenshot in attachment. first char is thin line, second protected
space.
I understand that it looks small.
Does it mean that you find the size of newer screenshots
On Tue, Aug 25, 2020 at 03:20:55PM +0200, Jean-Marc Lasgouttes wrote:
> >see the screenshot in attachment. first char is thin line, second protected
> >space.
>
> I understand that it looks small.
Does it mean that you find the size of newer screenshots acceptable?
Le 25/08/2020 à 13:54, Pavel Sanda a écrit :
On Tue, Aug 25, 2020 at 01:25:12PM +0200, Pavel Sanda wrote:
On Tue, Aug 25, 2020 at 12:14:33AM +0200, Jean-Marc Lasgouttes wrote:
Le 24/08/2020 ?? 13:28, Pavel Sanda a écrit :
Hi (JMarc?),
thin space is almost invisible on my screen and normal
On Tue, Aug 25, 2020 at 01:54:34PM +0200, Pavel Sanda wrote:
> On Tue, Aug 25, 2020 at 01:25:12PM +0200, Pavel Sanda wrote:
> > On Tue, Aug 25, 2020 at 12:14:33AM +0200, Jean-Marc Lasgouttes wrote:
> > > Le 24/08/2020 ?? 13:28, Pavel Sanda a écrit :
> > > >Hi (JMar
On Tue, Aug 25, 2020 at 01:25:12PM +0200, Pavel Sanda wrote:
> On Tue, Aug 25, 2020 at 12:14:33AM +0200, Jean-Marc Lasgouttes wrote:
> > Le 24/08/2020 ?? 13:28, Pavel Sanda a écrit :
> > >Hi (JMarc?),
> > >
> > >thin space is almost invisible on my screen an
On Tue, Aug 25, 2020 at 12:14:33AM +0200, Jean-Marc Lasgouttes wrote:
> Le 24/08/2020 ?? 13:28, Pavel Sanda a écrit :
> >Hi (JMarc?),
> >
> >thin space is almost invisible on my screen and normal protected space looks
> >smaller than thin space used to...
>
> D
Le 24/08/2020 à 13:28, Pavel Sanda a écrit :
Hi (JMarc?),
thin space is almost invisible on my screen and normal protected space looks
smaller than thin space used to...
Different from 2.3.x with the same zoom level? I did not see any recent
change in git log for space insets... (in texted
Hi (JMarc?),
thin space is almost invisible on my screen and normal protected space looks
smaller than thin space used to...
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
xample, this gives the impression that there is a space between an
> > > emphasized f and the caret, see attached screen capture. Previous versions
> > > of LyX did not show this. I consider this a regression. The selection
> > > highlight (blue rectangle) is also wider.
> >
On 2020-08-05 15:15, Enrico Forestieri wrote:
On Wed, Aug 05, 2020 at 09:50:48AM +0200, Daniel wrote:
I noticed that the caret is differently placed after some characters. For
example, this gives the impression that there is a space between an
emphasized f and the caret, see attached screen
On Wed, Aug 05, 2020 at 09:50:48AM +0200, Daniel wrote:
> I noticed that the caret is differently placed after some characters. For
> example, this gives the impression that there is a space between an
> emphasized f and the caret, see attached screen capture. Previous versions
>
I noticed that the caret is differently placed after some characters.
For example, this gives the impression that there is a space between an
emphasized f and the caret, see attached screen capture. Previous
versions of LyX did not show this. I consider this a regression. The
selection
On 6/29/20 3:02 AM, Jürgen Spitzmüller wrote:
> Am Sonntag, den 28.06.2020, 18:14 -0400 schrieb Richard Kimberly Heck:
>> On 6/28/20 12:50 PM, Jürgen Spitzmüller wrote:
>>> Am Sonntag, den 28.06.2020, 12:36 -0400 schrieb Richard Kimberly
>>> Heck:
If I'm reading this right, it just silently
Am Sonntag, den 28.06.2020, 18:14 -0400 schrieb Richard Kimberly Heck:
> On 6/28/20 12:50 PM, Jürgen Spitzmüller wrote:
> > Am Sonntag, den 28.06.2020, 12:36 -0400 schrieb Richard Kimberly
> > Heck:
> > > If I'm reading this right, it just silently fails if parskip is
> > > not
> > > installed. Or
On 6/28/20 12:50 PM, Jürgen Spitzmüller wrote:
> Am Sonntag, den 28.06.2020, 12:36 -0400 schrieb Richard Kimberly Heck:
>> If I'm reading this right, it just silently fails if parskip is not
>> installed. Or am I missing something?
> Yes, right (it does not fail, it just does not separate
Am Sonntag, den 28.06.2020, 12:36 -0400 schrieb Richard Kimberly Heck:
> If I'm reading this right, it just silently fails if parskip is not
> installed. Or am I missing something?
Yes, right (it does not fail, it just does not separate paragraphs).
But we can really assume parskip to be
On 6/28/20 10:58 AM, Juergen Spitzmueller wrote:
> commit b0c102cfb40985f46283e4fab0870ec5e2900699
> Author: Juergen Spitzmueller
> Date: Sun Jun 28 17:20:18 2020 +0200
>
> use package parskip to separate paragraphs with vertical space (#4796)
>
> File forma
Le 31/05/2020 à 19:30, Joel Kulesza a écrit :
On Fri, May 29, 2020 at 9:49 AM Pavel Sanda <mailto:sa...@lyx.org>> wrote:
On Thu, May 28, 2020 at 10:27:54AM -0600, Joel Kulesza wrote:
> Finally, significant EOL white space seems unidiomatic in a
"source file,"
On Fri, May 29, 2020 at 9:49 AM Pavel Sanda wrote:
> On Thu, May 28, 2020 at 10:27:54AM -0600, Joel Kulesza wrote:
> > Finally, significant EOL white space seems unidiomatic in a "source
> file,"
> > which is what a .lyx file effectively is.
> >
> > This i
On Thu, May 28, 2020 at 10:27:54AM -0600, Joel Kulesza wrote:
> Finally, significant EOL white space seems unidiomatic in a "source file,"
> which is what a .lyx file effectively is.
>
> This is an expert-use situation, but *I wonder if we have a way to overcome
> the
LyX Developers,
I've run into the situation multiple times that .lyx file EOL white space
(usually, a single space) can be significant. I've found this to be
particularly true before inline equations. This becomes problematic if
someone's editor (automatically) strips EOL white space, which
Le 18/04/2019 à 13:46, Pavel Sanda a écrit :
Libreoffice has approximately the same space as branch here.
It might be that the used font does not hint leading space properly or similar
so with your font the patch looks ok...
I reverted, rejoice ;)
JMarc
guess that's question for JMarc - I tried master after some time and
>>>> the
>>>> blank space between lines seem to widen to the extent that is somewhat
>>>> irritating to me. Is that intentional?
>>>
>>> Irritate you? No.
>> M
Le 29/03/2019 à 14:51, Pavel Sanda a écrit :
On Fri, Mar 29, 2019 at 02:34:25PM +0100, Jean-Marc Lasgouttes wrote:
Le 29/03/2019 ?? 14:22, Pavel Sanda a écrit :
Hi,
I guess that's question for JMarc - I tried master after some time and the
blank space between lines seem to widen to the extent
On Fri, Mar 29, 2019 at 02:34:25PM +0100, Jean-Marc Lasgouttes wrote:
> Le 29/03/2019 ?? 14:22, Pavel Sanda a écrit :
>> Hi,
>> I guess that's question for JMarc - I tried master after some time and the
>> blank space between lines seem to widen to the extent that is somewha
Le 29/03/2019 à 14:22, Pavel Sanda a écrit :
Hi,
I guess that's question for JMarc - I tried master after some time and the
blank space between lines seem to widen to the extent that is somewhat
irritating to me. Is that intentional?
Irritate you? No.
We have to discuss that (next week
Hi,
I guess that's question for JMarc - I tried master after some time and the
blank space between lines seem to widen to the extent that is somewhat
irritating to me. Is that intentional?
Pavel
Le 5 mars 2019 01:14:25 GMT+01:00, Richard Kimberly Heck a
écrit :
>Yes, that is it. Is it clear enough now from Daniel's remarks and mine
>what the problem is?
Yes, but it is not that easy to solve.
JMarc
on the next line.
So the cursor is at the end of the line. Suppose I now type a space. The
display does not change in any way. But the space is there, and if I
type a letter it will suddenly appear. It's a bit confusing, since
sometimes I'm not sure if I typed the space, then I type it again, and
LyX scolds
he next line.
>>
>> So the cursor is at the end of the line. Suppose I now type a space. The
>> display does not change in any way. But the space is there, and if I
>> type a letter it will suddenly appear. It's a bit confusing, since
>> sometimes I'm not sure i
Le 27/02/2019 à 23:41, Richard Kimberly Heck a écrit :
Very minor thing, but somewhat confusing. Suppose we are in this situation:
This is a line, with some words on it, which|
continues on the next line.
So the cursor is at the end of the line. Suppose I now type a space. The
display does
Very minor thing, but somewhat confusing. Suppose we are in this situation:
This is a line, with some words on it, which|
continues on the next line.
So the cursor is at the end of the line. Suppose I now type a space. The
display does not change in any way. But the space is there, and if I
type
I have made a suggestion of how spaces at the end of lines could be handled:
https://www.lyx.org/trac/ticket/10117#comment:34
But I am unsure. Was there a discussion of this before?
(As I mention in the comment, my engagement with this is purely
theoretical. But I hope that might still be
On Tue, Mar 14, 2017 at 01:01:23AM -0400, Scott Kostyshak wrote:
> On Mon, Mar 13, 2017 at 11:03:40AM +0100, Jean-Marc Lasgouttes wrote:
>
> > Question, why don't you += to append stuff to a string?
>
> I just forget. I will do this for the next patch.
I think I realize why it's not natural to
On 21 March 2017 at 21:11, Christian Ridderström <c...@lyx.org> wrote:
> I think I primarily want to make the CI workers have more disk space, as I
> think we in general would like to keep e.g. the workspace of the last
> successful build, and at the same time have more than f
On Tue, Mar 21, 2017 at 09:11:33PM +0100, Christian Ridderström wrote:
> On 21 March 2017 at 15:48, Scott Kostyshak <skost...@lyx.org> wrote:
>
> > > If anyone's interested, you can see remaining disk space (_if logged in_)
> > > for the CI workers at this link:
&
On 21 March 2017 at 15:48, Scott Kostyshak <skost...@lyx.org> wrote:
> > If anyone's interested, you can see remaining disk space (_if logged in_)
> > for the CI workers at this link:
> > https://ci.inria.fr/lyx/computer/
>
> Would it be possible and d
On Sun, Mar 19, 2017 at 10:59:53PM +0100, Christian Ridderström wrote:
> Hi,
>
> Just want to let you know that some of the CI jobs simply failed because
> the CI workers ran out of disk space. Some CI jobs take 4 GB, and with no
> remaining workdirs from CI jobs, the total disk
Hi,
Just want to let you know that some of the CI jobs simply failed because
the CI workers ran out of disk space. Some CI jobs take 4 GB, and with no
remaining workdirs from CI jobs, the total disk space per slave is about 20
GB. Anyway, I've done some cleaning and this aspect should be back
On Sat, Mar 18, 2017 at 05:49:30PM +0100, Jean-Marc Lasgouttes wrote:
> Le 18/03/2017 à 17:02, Scott Kostyshak a écrit :
> > On Tue, Mar 14, 2017 at 01:01:23AM -0400, Scott Kostyshak wrote:
> >
> > > I have a patch and it seems to work well. I want to clean it up before
> > > posting. I will post
Le 18/03/2017 à 17:02, Scott Kostyshak a écrit :
On Tue, Mar 14, 2017 at 01:01:23AM -0400, Scott Kostyshak wrote:
I have a patch and it seems to work well. I want to clean it up before
posting. I will post it again for review because even though it seems to
work well, I wonder if there is a
On Tue, Mar 14, 2017 at 01:01:23AM -0400, Scott Kostyshak wrote:
> I have a patch and it seems to work well. I want to clean it up before
> posting. I will post it again for review because even though it seems to
> work well, I wonder if there is a cleaner way of doing it. I will post
> a cleaned
1 - 100 of 1232 matches
Mail list logo
