Since I can't access bugzilla. I only tried for about 10 minutes so please
don't think this is exhaustive. On the whole, the current CVS isn't too bad. A
couple of bad assertions, but after a few of these are fixed, I think we can
let Michael S loose. Massive improvement on last time... what have
1. Click on an inset to display the relevant dialog.
2. Change document. Dialog remains open.
Clearly this is erroneous as insets and their dialogs are buffer dependent.
Presumably the way to resolve this is to connect the inset->hide and
hideBufferDependent signals?
2. I have two documents op
Hi!
I have found a few new bugs. Please have a look.
Michael
Place a paragraph that is aligned to the right and has a line above into
a minipage -> the line is not drawn correctly
(in order to observe this, there must be some text in front/after the
minipage and the
On Fri, Feb 11, 2005 at 01:11:24AM +, John Levon wrote:
> Since I can't access bugzilla. I only tried for about 10 minutes so please
I filed all these now.
john
On Fri, 2005-02-11 at 03:11, John Levon wrote:
> Since I can't access bugzilla. I only tried for about 10 minutes so please
> don't think this is exhaustive. On the whole, the current CVS isn't too bad. A
> couple of bad assertions, but after a few of these are fixed, I think we can
> let Michael S
On Mon, Feb 14, 2005 at 04:47:12PM +0200, Martin Vermeer wrote:
> 1) new document
> 2) insert math inset
> 3) inside math inset: insert text box (Control-M)
> 4) click inside this box.
mbox is broken in many ways right now.
Andre'
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> 3. Button insets are still not centred. I think someone closed
John> this bug. It needs re-opening.
What do you mean by not centered? I can see that the include inset can
behave in a very weird way if one use just after it, though.
Jo
On Mon, Feb 21, 2005 at 06:47:15PM +0100, Jean-Marc Lasgouttes wrote:
> John> 3. Button insets are still not centred. I think someone closed
> John> this bug. It needs re-opening.
>
> What do you mean by not centered? I can see that the include inset can
> behave in a very weird way if one use j
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> 2. I have two documents open with current cvs lyx. I'm not sure
Angus> how, but one has footnotes displayed in the NEW_INSET style,
Angus> whilst the other has them in old style. Isn't this
Angus> impossible Trust me, it's here
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
|
| Angus> 2. I have two documents open with current cvs lyx. I'm not sure
| Angus> how, but one has footnotes displayed in the NEW_INSET style,
| Angus> whilst the other has them in old
On Fri, Dec 14, 2001 at 08:42:32AM +0100, Michael Schmitt wrote:
> Place a paragraph that is aligned to the right and has a line above into
> a minipage -> the line is not drawn correctly
> (in order to observe this, there must be some text in front/after the
> minipage and the size of the mini
On Fri, Dec 14, 2001 at 08:42:32AM +0100, Michael Schmitt wrote:
> Adding a column after the last column of a table still causes a freed
> memory access error! (Use "njamd", a fast memory checker, to check this)
well, this patch doesn't make njamd complain, and things still work.
I'm not propo
On 14-Dec-2001 Michael Schmitt wrote:
> Insert one line of text into a note; delete the line and undo the
> deletion -> freed memory access error!
>
>#0 Paragraph::id (this=0x446b8fdc) at paragraph.C:2073
>#1 0x0818feb4 in InsetText::getParFromID (this=0x460feef8, id=1)
This is a stupid erro
On Fri, Dec 14, 2001 at 11:56:40AM +0100, Juergen Vigna wrote:
> fix stuff before commiting. But it seems it is better to commit often
> also half backed stuff as otherwise one will have to loose a lot of time
> solving conflicts, so most probably I will commit the whole stuff soon
> also if I di
On 14-Dec-2001 John Levon wrote:
> that's 3 times today already ! I know it's friday, but I'm sure JMarc and Andre are
Only 3 times that far to few! And I don't think they need you as their
advocate it seems they have attained full age some time ago! They were
at least so intelligent to not ans
On Fri, Dec 14, 2001 at 11:56:40AM +0100, Juergen Vigna wrote:
> But it seems it is better to commit often also half backed stuff as
> otherwise one will have to loose a lot of time solving conflicts, so most
> probably I will commit the whole stuff soon also if I didn't finish it
> and it still h
On 14-Dec-2001 Juergen Vigna wrote:
>> you could have just backed out their changes you know.,
>
> Could I?! I'll comit soon anyway!
And why should I back out a change which caused only one little
conflict I fixed in about 5 secs! You all are responsilbe if I
spend more time sending stupid mai
On 14-Dec-2001 Andre Poenitz wrote:
> On Fri, Dec 14, 2001 at 11:56:40AM +0100, Juergen Vigna wrote:
>> But it seems it is better to commit often also half backed stuff as
>> otherwise one will have to loose a lot of time solving conflicts, so most
>> probably I will commit the whole stuff soon a
On Fri, Dec 14, 2001 at 12:14:50PM +0100, Juergen Vigna wrote:
> And why should I back out a change which caused only one little
> conflict I fixed in about 5 secs! You all are responsilbe if I
> spend more time sending stupid mails then fixing real bugs!
first you hurt me , then you make me lau
On 14-Dec-2001 John Levon wrote:
> On Fri, Dec 14, 2001 at 12:14:50PM +0100, Juergen Vigna wrote:
>
>> And why should I back out a change which caused only one little
>> conflict I fixed in about 5 secs! You all are responsilbe if I
>> spend more time sending stupid mails then fixing real bugs!
On Fri, 14 Dec 2001, Juergen Vigna wrote:
[Blah, blah, blah, blah, blah]
So, when and where is the next LyX developer's meeting going to be held?
It seems Juergen needs some fun to lighten up. He could sure need to drink
some beer, introduce a bunch of bugs in the code, and sleep in forbidden
p
On 17-Dec-2001 Lars Gullik Bjønnes wrote:
>| So, when and where is the next LyX developer's meeting going to be held?
>
> Hey!! We never decide that until after New Years.
Well if you both wouldn't had drunken that much on the last meeting you
probably should know that we already have a volunt
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> On Fri, Dec 14, 2001 at 08:42:32AM +0100, Michael Schmitt wrote:
>> Place a paragraph that is aligned to the right and has a line above
>> into a minipage -> the line is not drawn correctly (in order to
>> observe this, there must be so
In this mail I've collected all the bugs with LyX 2.0beta1 I've
spotted so far. Overall, the experience has been very pleasant, but
there are some glitches worth correcting. My platform is (for now) Win
XP SP3 Polish.
If something is unclear, please ask - I'm writing this in a hurry,
hopin
Is there a special reason why the layout of the first (pasted) paragraph is
not kept when pasting? Most of the time I find this annyoing (e.g. when I try
to cut'n'paste a quotation).
Two bugs. Create a document with 5 pars:
one
two
three
four
five
(1.) select paragraph 2 and 3 ("two three"), cu
Hi Folks,
as promised, I took some time to look through the german po-files.
Attached are 2 patches for de.po and de_menus.bind.
They are against 1.1.4pre1.
Furthermore I found 2 (minor) glitches:
- The ballon tool tips are not translated. I'm not sure wether this
has ever since been th
> From: Michal
> Sent: Sun, 28 November, 2010 3:00:59
> Subject: LyX 2.0 - some bugs
>
> [BUG #1]
> Branch insets "override" all the rmb menus, so for example the user
> cannot spellcheck single word inside the branch inset via rmb anymore.
> This m
Michal wrote:
> In this mail I've collected all the bugs with LyX 2.0beta1 I've
> spotted so far. Overall, the experience has been very pleasant, but
> there are some glitches worth correcting. My platform is (for now) Win
> XP SP3 Polish.
>
> If something is unclear, please ask - I'm writ
On Sun, 28 Nov 2010 19:28:56 + (GMT)
Jim Oldfield wrote:
> > [BUG #1]
> > [...]
> This is a general problem with LyX right click menus, both in 2.0 and
> 1.6: as soon as context-specific items are defined, they erase the
> default ones, rather than adding to them. For instance, there isn't
On Sun, 28 Nov 2010 21:15:44 +0100
Pavel Sanda wrote:
> [...]
> Michal, thanks for your feedback. you reported however too many bugs
> to deal with them directly in this list. please push them into
> bugzilla so we can deal each of them individually.
I kind of hoped that at least some of the b
bly in a few days.
I don't want to be offending.
But honestly, fixing bugs is a time-consuming task too.
And I've not seen any bug disappearing by mentioning.
Some bugs are resorting when the sun light is raising...
...but I've not heard of it about software bugs. :-)
Stephan
s a time-consuming task too.
> And I've not seen any bug disappearing by mentioning.
> Some bugs are resorting when the sun light is raising...
> ...but I've not heard of it about software bugs. :-)
>
To continue the digression.. Some people consider reporting bugs as a
form of
> I don't want to be offending.
>
> But honestly, fixing bugs is a time-consuming task too.
> And I've not seen any bug disappearing by mentioning.
> Some bugs are resorting when the sun light is raising...
> ...but I've not heard of it about software b
Am 29.11.2010 um 12:42 schrieb Michal:
>> I don't want to be offending.
>>
>> But honestly, fixing bugs is a time-consuming task too.
>> And I've not seen any bug disappearing by mentioning.
>> Some bugs are resorting when the sun light is raising.
2010/11/28 Michal :
> In this mail I've collected all the bugs with LyX 2.0beta1 I've
> spotted so far. Overall, the experience has been very pleasant, but
> there are some glitches worth correcting. My platform is (for now) Win
> XP SP3 Polish.
>
> If something is unclear, please ask - I'm w
Vincent van Ravesteijn wrote:
> > [BUG #6]
> > Document settings cannot be reverted via "undo". Or is it by design?
>
> That might be by design. It's rather unwanted that settings are undone
> and the user doesn't see this happen.
this is a regression which works in 1.6, i remember to use it..
Hello
On Tue, Nov 30, 2010 at 1:37 AM, Vincent van Ravesteijn wrote:
>> [BUG #5]
>> The dotted line used to mark misspelled words is almost invisible
>> (under some conditions). Is the color/thickness of the line
>> configurable?
>>
>
> No, this is hardcoded. Under which conditions is it almos
> > [BUG #1]
> > Branch insets "override" all the rmb menus, so for example the
> > user cannot spellcheck single word inside the branch inset via rmb
> > anymore. This makes working with branches a whole lot harder.
>
> This was bug http://www.lyx.org/trac/ticket/6642.
>
> Now fixed in r36604
Ok, so I have reported (some of) the bugs to Trac. Just for
reference, I've detailed this process below.
> [BUG #1]
> Branch insets "override" all the rmb menus, so for example the
> user cannot spellcheck single word inside the branch inset via rmb
> anymore. This makes working with branc
> I have to admit I think it costs not much time to report a bug in
> LyX's bug tracker. Fortunately, it's not bugzilla. :-)
> And some of the bugs you reported are easier to fix with example
> files.
Well, I've just reported the bugs (see my other mail on this
list). For the record, the prepar
Am 30.11.2010 um 08:21 schrieb Michal:
>> I have to admit I think it costs not much time to report a bug in
>> LyX's bug tracker. Fortunately, it's not bugzilla. :-)
>> And some of the bugs you reported are easier to fix with example
>> files.
>Well, I've just reported the bugs (see my other m
> >Could you please specify to which bug reports should I attach
> > examples?
>
> Only if it's not too much work...
Thank you, it is very considerate of you. Such a rare thing
nowadays! :)
> * For ticket 7115 a screen shot and a small example file would be
> helpful. http://www.lyx.org/t
Am 30.11.2010 um 11:58 schrieb Michal:
>> * For ticket 7115 a screen shot and a small example file would be
>> helpful. http://www.lyx.org/trac/ticket/7115
>>
>> But as I cannot solve it, I'm only guessing.
>Unfortunately, I don't own a copy of Scientific Workplace.
Me too. I don't have Windo
Liviu Andronic wrote:
> I would suspect that a wavy line might be more desirable (as in MS
> Word, gtkspell, OOo, etc.), and if I remember this was the original
> implementation (although then the wavy line was too big :) ).
so we are at circles, since the wavy line was killed not so long ago :)
n
Am 30.11.2010 um 17:33 schrieb Pavel Sanda:
> Liviu Andronic wrote:
>> I would suspect that a wavy line might be more desirable (as in MS
>> Word, gtkspell, OOo, etc.), and if I remember this was the original
>> implementation (although then the wavy line was too big :) ).
>
> so we are at circle
Stephan Witt wrote:
> To break the circle I propose to adjust the line thickness to zoom factor.
> The attached patch does this. I think it's better now.
> The problem is the somewhat obfuscated rowpainter code.
> This makes the patch hard to read, sorry.
>
> Perhaps some kind soul is able to app
Am 02.12.2010 um 17:47 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> To break the circle I propose to adjust the line thickness to zoom factor.
>> The attached patch does this. I think it's better now.
>> The problem is the somewhat obfuscated rowpainter code.
>> This makes the patch hard to read
Stephan Witt wrote:
> > i tried it and thickness zoom works. however my suspiction that together
> > with change tracking the current code produce some mess was confirmed :)
>
> Sorry, I'm not sure I understand you.
> Do you refer to the screen appearance or to the rowpainter code?
i speak about
Stephan Witt wrote:
> Ok, but that's what I tried too. I attach some screen shot to compare
> the two versions, unpatched first - patched second. I cannot see any chaos.
this is how it looks on linux qt 4.6.3, Century Schoolbook L font.
(patched version)
pavel
<><>
Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Ok, but that's what I tried too. I attach some screen shot to compare
>> the two versions, unpatched first - patched second. I cannot see any chaos.
>
> this is how it looks on linux qt 4.6.3, Century Schoolbook L font.
> (patc
Stephan Witt wrote:
>
> Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
>
> > Stephan Witt wrote:
> >> Ok, but that's what I tried too. I attach some screen shot to compare
> >> the two versions, unpatched first - patched second. I cannot see any chaos.
> >
> > this is how it looks on linux qt 4.6.3
Am 02.12.2010 um 19:49 schrieb Pavel Sanda:
> Stephan Witt wrote:
>>
>> Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
>>
>>> Stephan Witt wrote:
Ok, but that's what I tried too. I attach some screen shot to compare
the two versions, unpatched first - patched second. I cannot see any chao
Stephan Witt wrote:
> >> Do you refer to the different vertical line positions?
> >
> > i refer to the the red line jumping like a goat on the hills. this is
> > intended?
>
> Yes. Do you have another idea?
aha :) i didn't got that its intended...
> The optimal solution would be a two pass alg
Pavel Sanda wrote:
> Stephan Witt wrote:
btw i have unrelated question.
the "native" string translation. this is standard naming in mac world or our
invetion? i wonder whether it should be translated or is it terminus technicus
like other aspell/enchant/hunspell strings which i'm going to kill rig
Am 02.12.2010 um 21:12 schrieb Pavel Sanda:
> Pavel Sanda wrote:
>
> btw i have unrelated question.
> the "native" string translation. this is standard naming in mac world or our
> invetion? i wonder whether it should be translated or is it terminus technicus
> like other aspell/enchant/hunspell
Stephan Witt wrote:
> Am 02.12.2010 um 21:12 schrieb Pavel Sanda:
>
> > Pavel Sanda wrote:
> >
> > btw i have unrelated question.
> > the "native" string translation. this is standard naming in mac world or our
> > invetion? i wonder whether it should be translated or is it terminus
> > technicu
Am 02.12.2010 um 21:32 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Am 02.12.2010 um 21:12 schrieb Pavel Sanda:
>>
>>> Pavel Sanda wrote:
>>>
>>> btw i have unrelated question.
>>> the "native" string translation. this is standard naming in mac world or our
>>> invetion? i wonder whether it sho
Stephan Witt wrote:
> > i see, so using applespell is correct, right?
>
> Hmm.. I'm not sure.
> Perhaps "Mac OS Speller" or "OS Spell Service"?
i will use Mac OS Speller, thanks.
pavel
Am 02.12.2010 um 20:08 schrieb Stephan Witt:
> Am 02.12.2010 um 19:49 schrieb Pavel Sanda:
>
>> Stephan Witt wrote:
>>>
>>> Am 02.12.2010 um 18:41 schrieb Pavel Sanda:
>>>
Stephan Witt wrote:
> Ok, but that's what I tried too. I attach some screen shot to compare
> the two versions
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo, etc.), and if I remember this was the original
implementation (although then the wavy line was too big :) ).
so we are at circles, sinc
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
> On 30/11/2010 17:33, Pavel Sanda wrote:
>> Liviu Andronic wrote:
>>
>>> I would suspect that a wavy line might be more desirable (as in MS
>>> Word, gtkspell, OOo, etc.), and if I remember this was the original
>>> implementation (although the
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo, etc.), and if I remember this was
Op 3-12-2010 15:54, Abdelrazak Younes schreef:
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might be more desirable (as in MS
Word, gtkspell, OOo, et
On 03/12/2010 15:58, Vincent van Ravesteijn wrote:
Op 3-12-2010 15:54, Abdelrazak Younes schreef:
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I would suspect that a wavy line might
Am 03.12.2010 um 15:54 schrieb Abdelrazak Younes:
> On 03/12/2010 15:52, Stephan Witt wrote:
>> Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
>>
>>
>>> On 30/11/2010 17:33, Pavel Sanda wrote:
>>>
Liviu Andronic wrote:
> I would suspect that a wavy line might
Stephan Witt wrote:
> I did no serious investigation until now...
> Only one example:
> I tried to adjust the left margin to zoom factor. Guess what happened...
> The cursor was misplaced badly.
and soon you'll get another ones ...
few times i tried to touch painting stuff and escaped as far as p
Another example:
Imagine you want to increase the thickness of the change bar.
Where to start and what classes has to be changed?
void RowPainter::paintChangeBar() sounds like it :) ;)
and
pi_.pain.fillRectangle(5, yo_ - row_.ascent(), 3, height,
Color_changebar);
5 is the offset from
On 03/12/2010 16:18, Pavel Sanda wrote:
Stephan Witt wrote:
I did no serious investigation until now...
Only one example:
I tried to adjust the left margin to zoom factor. Guess what happened...
The cursor was misplaced badly.
and soon you'll get another ones ...
few times i tried to
Op 3-12-2010 16:19, Abdelrazak Younes schreef:
On 03/12/2010 16:18, Pavel Sanda wrote:
Stephan Witt wrote:
I did no serious investigation until now...
Only one example:
I tried to adjust the left margin to zoom factor. Guess what
happened...
The cursor was misplaced badly.
and soon you'll g
On 03/12/2010 16:13, Stephan Witt wrote:
Am 03.12.2010 um 15:54 schrieb Abdelrazak Younes:
On 03/12/2010 15:52, Stephan Witt wrote:
Am 03.12.2010 um 15:31 schrieb Abdelrazak Younes:
On 30/11/2010 17:33, Pavel Sanda wrote:
Liviu Andronic wrote:
I
Abdelrazak Younes wrote:
>> and soon you'll get another ones ...
>> few times i tried to touch painting stuff and escaped as far as possible
>> :)
>>
>
> Quite frankly when I look at this LaTeX dependent code I find the painting
> code very simple in comparison :-)
then we should establish r
Am 03.12.2010 um 16:20 schrieb Vincent van Ravesteijn:
> Another example:
>> Imagine you want to increase the thickness of the change bar.
>> Where to start and what classes has to be changed?
>
> void RowPainter::paintChangeBar() sounds like it :) ;)
>
> and
>
>pi_.pain.fillRectangle(5, yo
On 03/12/2010 16:23, Vincent van Ravesteijn wrote:
Op 3-12-2010 16:19, Abdelrazak Younes schreef:
On 03/12/2010 16:18, Pavel Sanda wrote:
Stephan Witt wrote:
I did no serious investigation until now...
Only one example:
I tried to adjust the left margin to zoom factor. Guess what
happened...
On 12/03/2010 12:21 PM, Abdelrazak Younes wrote:
Hum I have a better one: the graphics stuff!!!
Speaking of which, can you look again at #6949?
Richard
Stephan Witt wrote:
> Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
Stephan what is the current state-of-art patch for 7120?
Others, do you like more the current thick line or zoomming-line style
for spellchech errs?
pavel
On Fri, Dec 10, 2010 at 6:34 PM, Pavel Sanda wrote:
> Stephan what is the current state-of-art patch for 7120?
> Others, do you like more the current thick line or zoomming-line style
> for spellchech errs?
>
I hate to nag, but the current implementation is very eye-catchy. But
I feel like loosing
Le 10 déc. 2010 à 21:35, Liviu Andronic a écrit :
On Fri, Dec 10, 2010 at 6:34 PM, Pavel Sanda wrote:
>> Stephan what is the current state-of-art patch for 7120?
>> Others, do you like more the current thick line or zoomming-line style
>> for spellchech errs?
>>
> I hate to nag, but the current i
Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
>
> Stephan what is the current state-of-art patch for 7120?
A little bit buried. But it may resurrect. Starting to dig soon. :-)
> Others, do you like
Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
>
> Stephan what is the current state-of-art patch for 7120?
See the attached patch.
Stephan
Index: src/rowpainter.cpp
===
Stephan Witt wrote:
> Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
>
> > Stephan Witt wrote:
> >> Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
> >
> > Stephan what is the current state-of-art patch for 7120?
>
> See the attached patch.
since nobody responded feel fr
Am 13.12.2010 um 13:07 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Am 10.12.2010 um 18:34 schrieb Pavel Sanda:
>>
>>> Stephan Witt wrote:
Looks ok - I cannot see any artifacts. Of course this isn't any evidence.
>>>
>>> Stephan what is the current state-of-art patch for 7120?
>>
>> See
Abdel has asked to be removed as default owner for the dialog and
frontend-qt4 bugs, and I've also removed him as default owner of the
file and menu bugs. Would anyone like to replace him? The only thing
this really means is that you get an email when a bug in that category
has been filed, so
On Tue, 19 Aug 2003, Juergen Spitzmueller wrote:
> Is there a special reason why the layout of the first (pasted) paragraph is
> not kept when pasting? Most of the time I find this annyoing
I agree... any objections to adding this to bugzilla?
/Christian
--
Christian Ridderström
Isn't described in bug #922?
> > Is there a special reason why the layout of the first (pasted) paragraph
is
> > not kept when pasting? Most of the time I find this annyoing
>
> I agree... any objections to adding this to bugzilla?
>
> /Christian
On Wed, 20 Aug 2003, Uwe Stöhr wrote:
> Isn't this described in bug #922?
Maybe... not quite I think, so to be on the size side I've added
http://bugzilla.lyx.org/show_bug.cgi?id=1332
since http://bugzilla.lyx.org/show_bug.cgi?id=922 doesn't seem to be
exactly the same, although relat
> "Peter" == Peter Suetterlin <[EMAIL PROTECTED]> writes:
Hi Pit,
Thanks for the patches, I'll commit them soon.
Peter> - The ballon tool tips are not translated. I'm not sure wether
Peter> this has ever since been the case, but i thought they have been
Peter> at some point...
They used t
On 19/04/2014 19:22, Richard Heck wrote:
Abdel has asked to be removed as default owner for the dialog and
frontend-qt4 bugs, and I've also removed him as default owner of the
file and menu bugs. Would anyone like to replace him? The only thing
this really means is that you get an email when
Abdelrazak Younes wrote:
>> undo/redo lasgouttes
>
> Remove
I think this one should remain. P
2014-04-19 19:22 GMT+02:00 Richard Heck:
>
> Abdel has asked to be removed as default owner for the dialog and
> frontend-qt4 bugs, and I've also removed him as default owner of the file
> and menu bugs. Would anyone like to replace him? The only thing this really
> means is that you get an email
Op 22 apr. 2014 09:47 schreef "Jürgen Spitzmüller" :
>
> 2014-04-19 19:22 GMT+02:00 Richard Heck:
>
>>
>> Abdel has asked to be removed as default owner for the dialog and
frontend-qt4 bugs, and I've also removed him as default owner of the file
and menu bugs. Would anyone like to replace him? The
2014-04-24 0:29 GMT+02:00 Vincent van Ravesteijn :
>
> You could sign me up for those two.
>
Done.
> However, I'm not sure what it means to be the ticket owner.
>
I think the main purpose is that someone knowledgeable in the respective
area checks the severity of the bug, maybe invites people to f
91 matches
Mail list logo
