Hi again,
Unfortunately, I was too fast sending this message. I forgot three things.
Firstly, thanks a lot for taking the time to report bugs. Strangely
enough, we like bug reports ;)
Second, do you still want a trac account?
And finally, I forgot to add you in copy of the message below
Le 27/09/2024 à 18:29, John Koutas a écrit :
Hello, I am writing to request an account to submit bugs for Lyx. In any
case, the two issues I have encountered when moving from 2.3 to 2.4.1
(Windows 10 22H2, Qt 6.7.2, Python 3.12.6) are the following:
Hello John,
*
Even when "mar
Hello, I am writing to request an account to submit bugs for Lyx. In any case,
the two issues I have encountered when moving from 2.3 to 2.4.1 (Windows 10
22H2, Qt 6.7.2, Python 3.12.6) are the following:
*
Even when "mark end of paragraphs" is not selected in Tools->Preferences-
On 7/22/24 3:56 AM, Jürgen Spitzmüller wrote:
Am Montag, dem 22.07.2024 um 07:53 + schrieb Juergen Spitzmueller:
commit 5bc4c11fd601773a7ffba850524afa03eafe13f9
Author: Juergen Spitzmueller
Date: Mon Jul 22 09:51:54 2024 +0200
tex2lyx: Fix two bugs in nomencl import
Am Montag, dem 22.07.2024 um 07:53 + schrieb Juergen Spitzmueller:
> commit 5bc4c11fd601773a7ffba850524afa03eafe13f9
> Author: Juergen Spitzmueller
> Date: Mon Jul 22 09:51:54 2024 +0200
>
> tex2lyx: Fix two bugs in nomencl import
>
> * The comment chara
Le 02/09/2023 à 11:29, Pavel Sanda a écrit :
And the last table here?
https://www.lyx.org/trac/wiki/BugTrackerHome#Unresolvedbugstargetedtonextmajorrelease2.4
That's the useful one, which I often need to scroll to :)
Or use the "End" key of the keyboard.
JMarc
--
lyx-devel mailing list
lyx-
On Fri, Sep 01, 2023 at 10:44:42PM +0200, Jean-Marc Lasgouttes wrote:
> Le 01/09/2023 ?? 22:40, Pavel Sanda a écrit :
> >On Fri, Sep 01, 2023 at 10:14:33PM +0200, Jean-Marc Lasgouttes wrote:
> >>Not me, but I am not sure why you needed it.
> >
> >3 pages of useless scrolling at https://www.lyx.org/
Le 01/09/2023 à 22:40, Pavel Sanda a écrit :
On Fri, Sep 01, 2023 at 10:14:33PM +0200, Jean-Marc Lasgouttes wrote:
Not me, but I am not sure why you needed it.
3 pages of useless scrolling at https://www.lyx.org/trac/wiki/BugTrackerHome
And the last table here?
https://www.lyx.org/trac/wiki/
On Fri, Sep 01, 2023 at 10:14:33PM +0200, Jean-Marc Lasgouttes wrote:
> Not me, but I am not sure why you needed it.
3 pages of useless scrolling at https://www.lyx.org/trac/wiki/BugTrackerHome
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-deve
Le 01/09/2023 à 21:39, Pavel Sanda a écrit :
Hi,
would anyone mind if I close (2.4.0 milestoned && fixedinmaster) bugs in trac?
Not me, but I am not sure why you needed it. Don't we have nice reports
that take into account fixedinmaster?
JMarc
--
lyx-devel mailing l
Hi,
would anyone mind if I close (2.4.0 milestoned && fixedinmaster) bugs in trac?
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
report is imho borderline
invalid, but the additional report in comment 2 looks like real issue
Fixed.
*Normal bugs
#10468 - selection assymetry, JMarc might get to that some day later
Can wait.
#12842 - UTF-8 in math label; Koji + Enrico work on that
Fixed.
#12852 - seems we can&
ve issues; might be deffered to later RCs, it only removes string, not
add new one (currently!)
Hi Riki,
I reviewed once more 2.4.0 milestoned bugs and except #11824, which is really
up to you, I do not see any further blocker for format/string freeze and
pushing new pre-release out.
OK. I'
e issues; might be deffered to later RCs, it only removes
> string, not add new one (currently!)
Hi Riki,
I reviewed once more 2.4.0 milestoned bugs and except #11824, which is really
up to you,
I do not see any further blocker for format/string freeze and pushing new
pre-release out.
Pav
On Thu, Aug 10, 2023 at 03:11:28PM +0200, Jürgen Spitzmüller wrote:
> Am Sonntag, dem 06.08.2023 um 13:52 +0200 schrieb Pavel Sanda:
> > * Blockers to decide before next release (string/format changes)
> > #12849 - hebrew quoation marks - has a patch which adds them
> > (checked/looks OK), I would
On 2023-07-27 16:13, Pavel Sanda wrote:
* Mac bugs:
#12279, #12820, #12418 - all point to probably the same issue; major, but it's
the same with 2.3.x; we have no clue and manpower ATM
There may be still ways to do better or worse here. After a brief
testing, I can reproduce a cli
On 2023-08-12 11:17, Daniel wrote:
On 2023-07-28 17:46, Richard Kimberly Heck wrote:
On 7/28/23 04:21, Pavel Sanda wrote:
On Thu, Jul 27, 2023 at 11:26:09PM -0400, Richard Kimberly Heck wrote:
#12577 - complex code to improve source editor within LyX; only JMarc
tried
to understand and failed
On 2023-07-28 17:46, Richard Kimberly Heck wrote:
On 7/28/23 04:21, Pavel Sanda wrote:
On Thu, Jul 27, 2023 at 11:26:09PM -0400, Richard Kimberly Heck wrote:
#12577 - complex code to improve source editor within LyX; only JMarc
tried
to understand and failed; anyone wants to engage?
This is to
Am Sonntag, dem 06.08.2023 um 13:52 +0200 schrieb Pavel Sanda:
> * Blockers to decide before next release (string/format changes)
> #12849 - hebrew quoation marks - has a patch which adds them
> (checked/looks OK), I would be inclined to commit; but I'd like to
> hear if the correct solution isn't
Am Donnerstag, dem 27.07.2023 um 16:13 +0200 schrieb Pavel Sanda:
> Juergen?
> #12779 - "Search as you type" issue; the original report is imho
> borderline invalid, but the additional report in comment 2 looks like
> real issue
The analysis and proposed fix in the ticket strike me correct.
> Jue
On Thu, Jul 27, 2023 at 04:13:37PM +0200, Pavel Sanda wrote:
> I think it's time for the breakdown of remaining bugs which hinder us from
> 2.4 release.
All in all I see only one major Mac bug left (but not a showstopper) and few
cases to decide before the freeze. The rest can eith
uestion here though. I see that you flagged bunch of
bugs with *finished* patches (e.g. #12797) as for 2.4.1/2 and I would argue
that it's better to commit them now for the following reasons:
- even if we release RC1 today we still have months for the testing because
there is no way transla
t; > about it. I'll have a look at it between now and then.
>
> For this particular case I think the question whether we *want* feature. In
> other
> words do we want to guarantee support and bugfixing the code we don't
> understand
> ourselves? :)
>
>
> T
big for 2.4.0. I've retargeted to 2.4.1. But I'm not really sure
> about it. I'll have a look at it between now and then.
For this particular case I think the question whether we *want* feature. In
other
words do we want to guarantee support and bugfixing the code we don&#x
On 7/27/23 10:13, Pavel Sanda wrote:
I think it's time for the breakdown of remaining bugs which hinder us from 2.4
release.
Thanks, Pavel, for taking the initiative here.
I was going to write separately about format freeze. Is there anything
anyone really wants to get in before we do
On Thu, Jul 27, 2023 at 09:54:41PM +0200, Enrico Forestieri wrote:
> >#12842 - UTF-8 in math label; patch from Koji needs review
>
> In its current form the patch is incomplete and produces wrong output. I'll
> have a look when time permits.
Thanks Enrico.
Pavel
--
lyx-devel mailing list
lyx-dev
On Thu, Jul 27, 2023 at 04:13:37PM +0200, Pavel Sanda wrote:
Juergen/Enrico?
#12831 - Udi proposes changing order how we output LaTeX font options.
Has a patch which looks legit to me, but I would like someone to look
over and give +1
I am leaving this to Jürgen.
#12842 - UTF-8 in math lab
On Thu, Jul 27, 2023 at 06:38:30PM +0200, Jean-Marc Lasgouttes wrote:
> If reverting the patch solves the issue, do that. Anyway it was partialbaked
> solution to another bug (#10468) I did not really understand either :)
I can confirm that reverting solves the issue. For now I'll revert and reope
Le 27/07/2023 à 16:13, Pavel Sanda a écrit :
*Normal bugs
JMarc is unf gone for quite some time, anyone willing to look?
#12841 - regression with math selection
I am still here for 10 minutes :)
For the record, I spend some time trying to understand the code and
failed. I trust Enrico&#
Hi all,
I think it's time for the breakdown of remaining bugs which hinder us from 2.4
release.
I might have been somewhat obnoxious to some of you in the trac during the past
week(s)
(sorry for that), but the good news is that we got to less than 20 bugs on our
2.4.0 radar!
I see onl
On 6/13/23 12:28, Pavel Sanda wrote:
Hi,
would anyone mind to actually close all fixedinmaster bugs with the 2.4.0
milestone?
It's polluting my searches when trying to sort out the bugs and it's usefulness
when
the new beta is out is IMO zero.
Fine by me. It'll still be possi
Hi,
would anyone mind to actually close all fixedinmaster bugs with the 2.4.0
milestone?
It's polluting my searches when trying to sort out the bugs and it's usefulness
when
the new beta is out is IMO zero.
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.o
Am Donnerstag, dem 08.12.2022 um 15:19 -0500 schrieb Richard Kimberly
Heck:
> > lyx_2_4.py:836:16: W0612: Unused variable 'k' (unused-variable)
>
> This is a weird one. Jürgen should have a look. Probably it's
> harmless.
> Basically, it's the loop variable, and it's not actually being used
> in
On Thu, 2022-12-08 at 22:27 +0100, Thibaut Cuvelier wrote:
> The only problem I see with type hints is that it restricts the
> versions of Python that can run the code. I believe that anything
> below 3.5 won't be able to even parse the Python code (which excludes
> 2.7). I understood that Python 2
On Thu, 8 Dec 2022 at 22:06, José Matos wrote:
> On the same vein for 2.5 I intend to start, in an iterative process, to
> add type hinting to our python code: http://mypy-lang.org/
>
> One example:
>
> def fib(n):
> if n==0 or n==1:
> return 1
> else:
> return fin(n-1)+fib(n-2)
>
> b
On Thu, 2022-12-08 at 21:37 +0100, Thibaut Cuvelier wrote:
> The Python standard for variables that are introduced just because
> the syntax requires it (like iterating X times) is to name that
> variable _ (or to prefix it with an underscore if there are more than
> one).
Yes, that would also be
On Thu, 8 Dec 2022 at 21:19, Richard Kimberly Heck
wrote:
> On 12/8/22 13:45, Scott Kostyshak wrote:
> > Perhaps it doesn't make sense to clean up lyx_2_4.py (except for looking
> > for bugs), but what would you think about adding an agreed-upon set of
> > pylint warn
easy to do this in Python, since you dot't normally get these
kinds of warnings.
Perhaps it doesn't make sense to clean up lyx_2_4.py (except for looking
for bugs), but what would you think about adding an agreed-upon set of
pylint warnings to our test suite for lyx_2_5.py?
I don&#
.py (except for looking
for bugs), but what would you think about adding an agreed-upon set of
pylint warnings to our test suite for lyx_2_5.py? Would this be useful
in catching potential bugs, or would it be more annoying than useful?
Here is the list of unused-variable warnings:
$ pylint ly
On 11/23/22 15:02, Pavel Sanda wrote:
On Wed, Nov 23, 2022 at 05:59:22PM +0100, Pavel Sanda wrote:
I think we should ask translators for .po updates. I can do the po remerge
if you want me, but first JMarc need to decide on backporting #12452
because it contains new string.
Ok, the new string i
On Wed, Nov 23, 2022 at 05:59:22PM +0100, Pavel Sanda wrote:
> I think we should ask translators for .po updates. I can do the po remerge
> if you want me, but first JMarc need to decide on backporting #12452
> because it contains new string.
Ok, the new string is in now. We can remerge and ask tr
;col=priority&col=milestone&order=id
It's a list of open critical and blocker bugs.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Wed, Nov 23, 2022 at 11:41:04AM -0500, Richard Kimberly Heck wrote:
> On 11/22/22 21:40, Richard Kimberly Heck wrote:
> >I've gone through the bugs with 2.3.7 milestones and backported the ones
> >that applied cleanly. There were a few that did not on which I've as
On 11/22/22 21:40, Richard Kimberly Heck wrote:
I've gone through the bugs with 2.3.7 milestones and backported the
ones that applied cleanly. There were a few that did not on which I've
asked for help. Once all that's sorted out, I can build the tarballs.
So we now need back
On 11/23/22 07:47, Pavel Sanda wrote:
On Tue, Nov 22, 2022 at 09:40:22PM -0500, Richard Kimberly Heck wrote:
I've gone through the bugs with 2.3.7 milestones and backported the ones
that applied cleanly. There were a few that did not on which I've asked for
help. Once all that'
On Tue, Nov 22, 2022 at 09:40:22PM -0500, Richard Kimberly Heck wrote:
> I've gone through the bugs with 2.3.7 milestones and backported the ones
> that applied cleanly. There were a few that did not on which I've asked for
> help. Once all that's sorted out, I can build
Am Mi., 23. Nov. 2022 um 03:40 Uhr schrieb Richard Kimberly Heck <
rikih...@gmail.com>:
> I've gone through the bugs with 2.3.7 milestones and backported the ones
> that applied cleanly. There were a few that did not on which I've asked
> for help. Once all that'
I've gone through the bugs with 2.3.7 milestones and backported the ones
that applied cleanly. There were a few that did not on which I've asked
for help. Once all that's sorted out, I can build the tarballs.
Is Eugene still around? He was building the Windows installers not lo
Am Dienstag, dem 22.11.2022 um 10:24 +0100 schrieb Jean-Marc
Lasgouttes:
> I guess the issue is the difference in behavior of fonts changes in
> mathed (where they nest) and texted (where they toggle).
>
> I would guess we have an enhancement/bug ticket about that somewhere.
Didn't find one.
--
Le 22/11/2022 à 09:15, Juergen Spitzmueller a écrit :
commit 26f6aa465ecb74de323b4756ed043a6d91b883dd
Author: Juergen Spitzmueller
Date: Tue Nov 22 10:09:16 2022 +0100
Cleanup mathes/BUGS (#3493)
Removing. M-c e has a different meaning nowadays
(tabular-feature delete
On 1/3/21 11:50 PM, Richard Kimberly Heck wrote:
> Hi, all,
>
> One thing we might do on the way to 2.4.0 is look over the bugs that
> have patches. Here's a URL for that search:
>
> https://www.lyx.org/trac/query?status=accepted&status=assigned&status=new&sta
Hi, all,
One thing we might do on the way to 2.4.0 is look over the bugs that
have patches. Here's a URL for that search:
https://www.lyx.org/trac/query?status=accepted&status=assigned&status=new&status=reopened&keywords=~patch&col=id&col=summary&col=status&am
I filed a couple of bugs over the years and lost a bit track. So, I just
went through them (looking for duplicates and fixed ones). Thanks for
fixing so many of them!
Maybe it's interesting to someone to see my favorite ones that have
survived so far. I have added little explanations fo
text mode
dropping extra hline
unexpected dummy size: 2 content:
unexpected dummy size: 2 content:
Which of these are potential bugs? i.e., which should I attempt to
create a minimal example for?
Scott
signature.asc
Description: PGP signature
Am Freitag, den 25.01.2019, 21:04 +0100 schrieb mno...@gmx.net:
> "general IPA toolbar" meaning "Phonetic Symbols (auto)"?
Yes.
> But to add to my initial observation:
>
> the extra-long toolbar also does not display the expand-chevrons on
> initial view. These are only hinted at as two small do
Am Freitag, den 25.01.2019, 21:10 +0100 schrieb mno...@gmx.net:
> And also add a uniform weight (to what are real characters)…?
All icons are done with the same font and weight (Liberation Sans
Regular).
But they need to be scaled to the same size.
> Looks like in quite a few cases the onscreen
On 25.01.19 18:39, Jürgen Spitzmüller wrote:
> Am Donnerstag, den 24.01.2019, 21:32 +0100 schrieb mno...@gmx.net:
>> For example global-rise and global-fall are cut off in the toolbar,
>> but
>> look 'OK', yet very different in the text when inserted.
>>
>>
>> Downstep gives me the blank unicode sq
On 25.01.19 15:16, Jürgen Spitzmüller wrote:
>> Also in behavior: "Pulmonic consonants" toolbar is quite long,
>> expanding
>> it leads to the toolbar directly below that becoming invisible. Is
>> this
>> desired? I think it should not make any other toolbar invisible but
>> expand in own rows to
Am Donnerstag, den 24.01.2019, 21:32 +0100 schrieb mno...@gmx.net:
> For example global-rise and global-fall are cut off in the toolbar,
> but
> look 'OK', yet very different in the text when inserted.
>
>
> Downstep gives me the blank unicode square.
>
> voiceless doesn't display at all in the
Am Dienstag, den 22.01.2019, 17:09 +0100 schrieb mn:
> The attached screenshot shows a range of problems with the display of
> theIPA toolbars.
> Some are just a bit off in their placement (eg "Rising (accent)",
> some
> are unrecognizably cut off ("Global rise" & "Global fall")
> The two consonant
Le 25/01/2019 à 07:22, Daniel a écrit :
On 2019-01-24 21:32, mno...@gmx.net wrote:
Can someone provide a link or a an MWE with all IPA characters and a
complete, documented target PDF to test for?
Sorry, I have never used IPA and haven't found any manual for it. Maybe
someone else can jump in
On 2019-01-24 21:32, mno...@gmx.net wrote:
Can someone provide a link or a an MWE with all IPA characters and a
complete, documented target PDF to test for?
Sorry, I have never used IPA and haven't found any manual for it. Maybe
someone else can jump in from here.
Daniel
On 24.01.19 21:15, mno...@gmx.net wrote:
> On 23.01.19 07:18, Daniel wrote:
>> On 2019-01-22 17:09, mn wrote:
>>> The attached screenshot shows a range of problems with the display of
>>> theIPA toolbars.
>>>
>>> Some are just a bit off in their placement (eg "Rising (accent)", some
>>> are unrecog
On 23.01.19 07:18, Daniel wrote:
> On 2019-01-22 17:09, mn wrote:
>> The attached screenshot shows a range of problems with the display of
>> theIPA toolbars.
>>
>> Some are just a bit off in their placement (eg "Rising (accent)", some
>> are unrecognizably cut off ("Global rise" & "Global fall")
>
On 2019-01-22 17:09, mn wrote:
The attached screenshot shows a range of problems with the display of
theIPA toolbars.
Some are just a bit off in their placement (eg "Rising (accent)", some
are unrecognizably cut off ("Global rise" & "Global fall")
The two consonant toolbars are visually in a cer
The attached screenshot shows a range of problems with the display of
theIPA toolbars.
Some are just a bit off in their placement (eg "Rising (accent)", some
are unrecognizably cut off ("Global rise" & "Global fall")
The two consonant toolbars are visually in a certain inharmonic disarray
of weigh
On Mon, Dec 18, 2017 at 02:47:56AM +, Hongbin Chen wrote:
> Hello,
>
>
> These are actually not new bugs, but they still exist in 2.3.0rc1.
> 1. The shortcut Command+Shift+R for exporting pdf is not working. If I choose
> from the menu to export pdf, it’s fine. But if I u
Hello,
These are actually not new bugs, but they still exist in 2.3.0rc1.
1. The shortcut Command+Shift+R for exporting pdf is not working. If I choose
from the menu to export pdf, it’s fine. But if I use the shortcut to export,
then nothing happens. I tried to define the shortcut in various
so as not to lay a trap for the developers who are going to come
after me.
"to maintain the code after me" (avoiding any unintentional double
meaning due to my uncolloquial English).
; Date: Mon Jun 5 23:14:48 2017 +0200
>>>
>>> Fix bugs #9598 and #10650
>>> ---
>>
>>> +// gcc < 4.8.0 and msvc < 2015 do not support C++11 thread_local
>>> +#if defined(__GNUC__) && ((__GNUC__ == 4 && __GNUC_MINOR
a écrit :
> > > > commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
> > > > Author: Enrico Forestieri
> > > > Date: Mon Jun 5 23:14:48 2017 +0200
> > > >
> > > > Fix bugs #9598 and #10650
> > > > ---
> > >
> > > > +// gcc < 4.8.0 a
a écrit :
> > > > commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
> > > > Author: Enrico Forestieri
> > > > Date: Mon Jun 5 23:14:48 2017 +0200
> > > >
> > > > Fix bugs #9598 and #10650
> > > > ---
> > >
> > > > +// gcc < 4.8.0 a
Le 08/06/2017 à 02:07, Enrico Forestieri a écrit :
On Thu, Jun 08, 2017 at 12:50:19AM +0200, Guillaume MM wrote:
Le 05/06/2017 à 23:15, Enrico Forestieri a écrit :
commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
Author: Enrico Forestieri
Date: Mon Jun 5 23:14:48 2017 +0200
Fix bugs
On Thu, Jun 08, 2017 at 12:50:19AM +0200, Guillaume MM wrote:
> Le 05/06/2017 à 23:15, Enrico Forestieri a écrit :
> > commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
> > Author: Enrico Forestieri
> > Date: Mon Jun 5 23:14:48 2017 +0200
> >
> &g
Le 05/06/2017 à 23:15, Enrico Forestieri a écrit :
commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
Author: Enrico Forestieri
Date: Mon Jun 5 23:14:48 2017 +0200
Fix bugs #9598 and #10650
---
+// gcc < 4.8.0 and msvc < 2015 do not support C++11 thread_local
+#if defined(__
On Mon, Jun 05, 2017 at 07:37:08AM +0200, Kornel Benko wrote:
> Am Montag, 5. Juni 2017 um 03:50:47, schrieb Enrico Forestieri
>
> > On Sun, Jun 04, 2017 at 01:08:06PM +0200, Guillaume MM wrote:
> >
> > > Le 04/06/2017 à 02:27, Enrico Forestieri a écrit :
> > > > On Sat, Jun 03, 2017 at 11:27:2
Am Montag, 5. Juni 2017 um 03:50:47, schrieb Enrico Forestieri
> On Sun, Jun 04, 2017 at 01:08:06PM +0200, Guillaume MM wrote:
>
> > Le 04/06/2017 à 02:27, Enrico Forestieri a écrit :
> > > On Sat, Jun 03, 2017 at 11:27:25PM +0200, Guillaume MM wrote:
> > >
> > > > I am wondering since this result
On Sun, Jun 04, 2017 at 01:08:06PM +0200, Guillaume MM wrote:
> Le 04/06/2017 à 02:27, Enrico Forestieri a écrit :
> > On Sat, Jun 03, 2017 at 11:27:25PM +0200, Guillaume MM wrote:
> >
> > > I am wondering since this results in a different vertical spacing.
> >
> > No, this will not change the v
On Sun, Jun 04, 2017 at 12:33:10PM +0200, Kornel Benko wrote:
> All of the above pass here now.
+1 All ctests are back to where they were before.
Scott
Le 04/06/2017 à 02:27, Enrico Forestieri a écrit :
On Sat, Jun 03, 2017 at 11:27:25PM +0200, Guillaume MM wrote:
I am wondering since this results in a different vertical spacing.
No, this will not change the vertical spacing.
It actually does, as shown with diffpdf.
tieri wrote:
> > > > commit 55bbd67cde18184082b074f669a6b81cc48257b6
> > > > Author: Enrico Forestieri
> > > > Date: Sat Jun 3 17:26:05 2017 +0200
> > > >
> > > > Fix bugs #10650 and #9598
> > >
> >
> Author: Enrico Forestieri
> > > Date: Sat Jun 3 17:26:05 2017 +0200
> > >
> > > Fix bugs #10650 and #9598
> >
> > I think this commit broke the following tests:
> >
> > export/doc/de/Additional_dvi (Failed)
> > e
On Sat, Jun 03, 2017 at 11:27:25PM +0200, Guillaume MM wrote:
> Le 03/06/2017 à 17:26, Enrico Forestieri a écrit :
> > commit 55bbd67cde18184082b074f669a6b81cc48257b6
> > Author: Enrico Forestieri
> > Date: Sat Jun 3 17:26:05 2017 +0200
> >
> > Fix bug
On Sat, Jun 03, 2017 at 05:25:44PM -0400, Scott Kostyshak wrote:
> On Sat, Jun 03, 2017 at 05:26:52PM +0200, Enrico Forestieri wrote:
> > commit 55bbd67cde18184082b074f669a6b81cc48257b6
> > Author: Enrico Forestieri
> > Date: Sat Jun 3 17:26:05 2017 +0200
> >
> &
Le 03/06/2017 à 17:26, Enrico Forestieri a écrit :
commit 55bbd67cde18184082b074f669a6b81cc48257b6
Author: Enrico Forestieri
Date: Sat Jun 3 17:26:05 2017 +0200
Fix bugs #10650 and #9598
Hi Enrico,
It seems that the above commit changes the output of the attached file.
Before
On Sat, Jun 03, 2017 at 05:26:52PM +0200, Enrico Forestieri wrote:
> commit 55bbd67cde18184082b074f669a6b81cc48257b6
> Author: Enrico Forestieri
> Date: Sat Jun 3 17:26:05 2017 +0200
>
> Fix bugs #10650 and #9598
I think this commit broke the following tests:
Am Sonntag, den 15.01.2017, 08:46 -0500 schrieb PhilipPirrip:
> New document, code view on.
>
> Insert a bib database
>
> in Document Settings, Bibliography, select "sectioned bibliography";
> this adds \usepackage[dot]{bibtopic}
>
> switch from bibtex to biblatex, same dialog
>
> \usepackage[
I'll be reporting less important bugs here, if they don't make it into
the release, I'll report again on lyx.org bug tracker for future fixes.
--- sectioned bibliography bug ---
New document, code view on.
Insert a bib database
in Document Settings, Bibliography, se
Le 24/10/2016 à 02:25, Scott Kostyshak a écrit :
I have had unfortunately avoided making Qt bug reports for the same
reason. Perhaps ask on Qt's dev mailing list?
There was a time were André would magically pop up in moments like this
and just report problems... Sigh. André, we miss you !
I
On Sun, Oct 23, 2016 at 09:36:46PM +0200, Jean-Marc Lasgouttes wrote:
> It would be nice to report at least the first issue (see
> GuiFontMetrics::width), but I do not know how to make a self contained Qt
> program for this kind of thing. How minimal can I afford to be?
I have had unfortunately a
The following patch posted to
http://www.lyx.org/trac/ticket/10436
works around two probable Qt5 bugs related to Arabic text:
* with Qt5, QFontMetrics::width does not return the correct value for
some Arabic text
* Likewise, the undocumented layout flags TextForceRightToLeft and
On 08/24/2016 12:47 AM, Vermeer Martin wrote:
> A quick bug report:
>
> 1) when I include a document into another document, upon loading it takes the
> branch colours of the latter (slave) document, not of the master.
This is an instance of the general master vs slave preferences problem.
> 2) e
A quick bug report:
1) when I include a document into another document, upon loading it takes the
branch colours of the latter (slave) document, not of the master.
2) every time I edit the preamble and apply the change, it does a conversion of
the whole document which reports the flex inset URL
forgot to add the xcolor package to the preamble. This is now
> fixed:
> http://www.lyx.org/trac/changeset/493339950737c84c315c5c8cddda0cd32e945791/lyxgit
Thanks for the quick fix, Uwe!
I tested it and it works well. I'll run some more lyx2lyx tests to see
if I can find other bugs.
Scott
Am 04.11.2015 um 00:23 schrieb Scott Kostyshak:
Uwe, can you take a look at this bug? I think it has to do with the 491
and 492 format changes.
Thanks for the pointer.
In lyx2lyx I forgot to add the xcolor package to the preamble. This is
now fixed:
http://www.lyx.org/trac/changeset/4933399
On Tue, Nov 03, 2015 at 06:22:11PM -0500, Scott Kostyshak wrote:
> On Sun, Nov 01, 2015 at 07:43:57PM -0500, Scott Kostyshak wrote:
> > On Sun, Nov 01, 2015 at 04:30:31PM -0500, Richard Heck wrote:
> >
> > > The problem is that EmbeddedObjects.lyx was already format 498, and
> > > lyx2lyx
> > > s
On Sun, Nov 01, 2015 at 07:43:57PM -0500, Scott Kostyshak wrote:
> On Sun, Nov 01, 2015 at 04:30:31PM -0500, Richard Heck wrote:
>
> > The problem is that EmbeddedObjects.lyx was already format 498, and lyx2lyx
> > seems to do the wrong thing when asked to convert it to the format it
> > already i
Richard Heck wrote:
> I think it would be a perfectly reasonable requirement from now on
> ---say, starting in the 2.3.x development cycle---that every format
> change be accompanied by some kind of test file that illustrates the use
> of the new feature (that's what it usually is) and that can be
Am Sonntag, 1. November 2015 um 20:14:40, schrieb Richard Heck
> On 11/01/2015 08:05 PM, Scott Kostyshak wrote:
> > On Sun, Nov 01, 2015 at 09:56:55PM +0100, Georg Baum wrote:
> >> Scott Kostyshak wrote:
> >>
> >>> On Sun, Nov 01, 2015 at 11:52:08AM -0500, Richard Heck wrote:
> On 11/01/2015
On 11/01/2015 08:05 PM, Scott Kostyshak wrote:
On Sun, Nov 01, 2015 at 09:56:55PM +0100, Georg Baum wrote:
Scott Kostyshak wrote:
On Sun, Nov 01, 2015 at 11:52:08AM -0500, Richard Heck wrote:
On 11/01/2015 11:37 AM, Scott Kostyshak wrote:
Since you brought it up though, Kornel and I have di
1 - 100 of 2381 matches
Mail list logo
