Am 03.12.2010 um 04:36 schrieb Enrico Forestieri:
> On Fri, Dec 03, 2010 at 12:44:57AM +0100, Pavel Sanda wrote:
>
>> Stephan Witt wrote:
>>> There is a patch pending from Georg.
>>> I present it here again and propose to apply it.
>>>
>>> The second part of the patch is mine.
>>> It encapsulate
On Fri, Dec 03, 2010 at 04:36:37AM +0100, veno...@arcadiaclub.com wrote:
> So, what to do?
>
> 1) simply call latex twice on 2 slightly different .tex files (slow with
> comples code?);
> 2) while detecting PostScript literals rewrite the DVI (throgh the DTL)
> without the tightpage option (if it
On Fri, Dec 03, 2010 at 12:30:32AM +0100, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > On Thu, Dec 02, 2010 at 05:27:43PM +0100, Pavel Sanda wrote:
> >
> > > one related request: could you post patch for examples/instant_preview.lyx
> > > which contains working example for tikz and example f
> I wonder whether there is a way to avoid a double call to latex in case the
> legacy route is taken. I tried replacing the above two lines with simply
>return legacy_conversion_step2(latex_file, dpi, output_format)
> but it did not work. Could you investigate?
Well, the problem i
On Fri, Dec 03, 2010 at 12:44:57AM +0100, Pavel Sanda wrote:
> Stephan Witt wrote:
> > There is a patch pending from Georg.
> > I present it here again and propose to apply it.
> >
> > The second part of the patch is mine.
> > It encapsulates the crucial hasDigit into an ignoreWord() method to
>
Vincent van Ravesteijn wrote:
> I think we should do something about the large amount of critical
> bugs. I believe there are 12 that have a bug number of 7000 or higher.
except #7026 which is already in pipe none of them looked as showstopper.
would you prefer delay +1 week? or freeze except for
On Fri, Dec 3, 2010 at 12:55 AM, Pavel Sanda wrote:
> Pavel Sanda wrote:
>> anything you want to have in before?
>
> 1) JMarc, there was some reminder in undo fix you committed.
> do you intend to push it in soon?
> 2) Georg wrote patch for #7071. somebody who see into ReferenceCache
> can per
Pavel Sanda wrote:
> anything you want to have in before?
1) JMarc, there was some reminder in undo fix you committed.
do you intend to push it in soon?
2) Georg wrote patch for #7071. somebody who see into ReferenceCache
can perhaps commit it (or give ok in trac, so Georg can proceed)?
my
Stephan Witt wrote:
> There is a patch pending from Georg.
> I present it here again and propose to apply it.
>
> The second part of the patch is mine.
> It encapsulates the crucial hasDigit into an ignoreWord() method to
> prepare to solve the FIXME and to propose an alternate implementation.
>
Julien Rioux wrote:
> Yes indeed unifying them would be best. So either
> 1) Add a command-line true/false flag for lilypond preprocessing
> 2) Add a more general mechanism for specifying a preprocessor
>
> What I really would like, though, is to change how the preview script
> handles command-lin
On 02/12/2010 6:24 PM, Pavel Sanda wrote:
Julien, i was wondering whether there would be possibility to
join lyxpreview-lytex2bitmap.py and original script. their diff
gives only small lilypond block. for example by some special flag
given as parameter on commandline to oroginal script. ... maybe
Enrico Forestieri wrote:
> On Thu, Dec 02, 2010 at 05:27:43PM +0100, Pavel Sanda wrote:
>
> > one related request: could you post patch for examples/instant_preview.lyx
> > which contains working example for tikz and example for pstrick?
> > we should distribute it as well.
>
> See attached.
i'l
Julien Rioux wrote:
> If this gets in we would need a similar patch for
> lyxpreview-lytex2bitmap.py and also (possibly, I don't know for sure)
Julien, i was wondering whether there would be possibility to
join lyxpreview-lytex2bitmap.py and original script. their diff
gives only small lilypond
On Thu, Dec 02, 2010 at 09:41:50PM +0100, veno...@arcadiaclub.com wrote:
> > Why the check for \" ?
>
> Dvipng looks for 'ps:' or '"', so I think they have the same meaning.
> From dvipng source (special.c):
>
> if (special[0]=='"' || strncmp(special,"ps:",3)==0) { /* Literal PostScript */
Ok,
On Thu, Dec 02, 2010 at 05:27:43PM +0100, Pavel Sanda wrote:
> one related request: could you post patch for examples/instant_preview.lyx
> which contains working example for tikz and example for pstrick?
> we should distribute it as well.
See attached.
--
Enrico
Index: lib/examples/instant_pre
> 1) Insert Tex code (Ctrl-l)
> 2) Type text (ex. "\paragraph{test}")
> 3) Start new line within LaTeX box (Enter)
> 4) Remove new line within LaTeX box (Backspace)
> 5) LyX crashes
>
> There are other variations that cause Lyx to crash that occur during normal
> Lyx usage.
>
> NB: I use LyX 1.6.5,
Hi,
I enjoy using Lyx for my thesis. I have a problem with lyx crashing
sometimes when I try to use LaTeX code. This is an example of how I get the
error.
1) Insert Tex code (Ctrl-l)
2) Type text (ex. "\paragraph{test}")
3) Start new line within LaTeX box (Enter)
4) Remove new line within LaTeX b
On 12/02/2010 05:01 PM, Vincent van Ravesteijn wrote:
See also output_xhtml.h:
typedef std::deque TagDeque;
///
typedef std::vector TagStack;
/// holds start tags until we know there is content in them.
TagDeque pending_tags_;
/// remembers the h
On 12/02/2010 04:54 PM, Vincent van Ravesteijn wrote:
I read somewhere that stacks are best implemented as deques. Don't ask me
why now,
but I think they are slightly cheaper. (I'm sure Andre would have a view
about this.)
Some googling gives me:
The C++ Standard, in section 23.1.1, offers some
See also output_xhtml.h:
typedef std::deque TagDeque;
///
typedef std::vector TagStack;
/// holds start tags until we know there is content in them.
TagDeque pending_tags_;
/// remembers the history, so we can make sure we nest properly.
TagS
Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
> > Especially for amateurs like me who don't know what a deque is, I
> > would prefer to use vector... keep it simple and stupid ;).
>
> your code doesn't suggest newbie, so to learn one more standard class
> like degue :) we use it elsewhere as
Vincent van Ravesteijn wrote:
> Especially for amateurs like me who don't know what a deque is, I
> would prefer to use vector... keep it simple and stupid ;).
your code doesn't suggest newbie, so to learn one more standard class
like degue :) we use it elsewhere as well...
pavel
> I read somewhere that stacks are best implemented as deques. Don't ask me
> why now,
> but I think they are slightly cheaper. (I'm sure Andre would have a view
> about this.)
Some googling gives me:
The C++ Standard, in section 23.1.1, offers some advice on which
containers to prefer. It says:
On 12/01/2010 07:45 AM, Abdelrazak Younes wrote:
Why not simply add a preamble editor in the branches dialog? LyX will
then collect the preamble for each branches. I guess this would be a
format change but it strikes me as the correct solution...
Kind of crowded already, but perhaps a combo
Am 02.12.2010 um 21:37 schrieb Vincent van Ravesteijn:
>>>
>>> If all documents are closed, I assume you have only a menubar left ? I
>>> really can't understand why trunk would then be able to execute
>>> "LFUN_DIALOG_SHOW aboutlyx", because this LFUN is handled in GuiView ?
>>>
>>> So, if this
On 12/02/2010 03:27 PM, Vincent van Ravesteijn wrote:
- /// Call then when existing things like footnotes.
+ /// Call this when existing things like footnotes.
void restoreLastLayout() { layout_stack_.pop_back(); }
exiting ?
Besides, why are counter_stack_ and layout_stack_
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 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
> You have to avoid tabs in python sources.
Yes, sorry I've fixed that.
> No reason to split this statement, keep it on a single line.
Ooook :)
> Why the check for \" ?
Dvipng looks for 'ps:' or '"', so I think they have the same meaning.
>From dvipng source (special.c):
if (special[0]=='"'
>>
>> If all documents are closed, I assume you have only a menubar left ? I
>> really can't understand why trunk would then be able to execute
>> "LFUN_DIALOG_SHOW aboutlyx", because this LFUN is handled in GuiView ?
>>
>> So, if this works in trunk, is there still a GuiView left ?
>
> When LyX is
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:11 schrieb LyX Ticket Tracker:
> #6902: About LyX inaccessible without an open document
> -+--
> Reporter: philb| Owner: lasgouttes
> Type: defect | Status: new
> - /// Call then when existing things like footnotes.
> + /// Call this when existing things like footnotes.
> void restoreLastLayout() { layout_stack_.pop_back(); }
exiting ?
Besides, why are counter_stack_ and layout_stack_ deque's ?
>/// Used to keep track of active counte
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
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
fyi,
comparison of userguide of 2.0 and 1.6 gives pdflatex uncompilable document (ps
output works). i'm not sure what can be done with it.
cf http://lwn.net/Articles/416485/
pavel
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
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:
> Am 02.12.2010 um 19:53 schrieb Pavel Sanda:
>
> > Stephan Witt wrote:
> >> Now I did the aspell backend changes.
> >> The complete patch (aspell+hunspell) is attached.
> >> I'm ready to commit it.
> >
> > i'm afraid the review is not going to happen, so wait tonight and comm
Am 02.12.2010 um 19:53 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Now I did the aspell backend changes.
>> The complete patch (aspell+hunspell) is attached.
>> I'm ready to commit it.
>
> i'm afraid the review is not going to happen, so wait tonight and commit it
> tommorrow...
Sorry, 30 sec
Stephan Witt wrote:
> Now I did the aspell backend changes.
> The complete patch (aspell+hunspell) is attached.
> I'm ready to commit it.
i'm afraid the review is not going to happen, so wait tonight and commit it
tommorrow...
pavel
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 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
On 12/02/2010 11:29 AM, Vincent van Ravesteijn wrote:
No, this should never be empty. We specifically push a null pointer onto the
stack at the beginning, as a kind
of dummy entry that makes sure we never pop more than we push. If it is
empty, then we have popped more
than we have pushed.
On 12/02/2010 10:52 AM, Vincent van Ravesteijn wrote:
On Thu, Dec 2, 2010 at 4:48 PM, Jean-Marc Lasgouttes wrote:
Le 2 déc. 2010 à 16:19, Richard Heck a écrit :
The point here is that the old line completely wipes out the counters,
including all record of which counters
there are bu
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
<><>
Dear LyX Developers,
I don't want to re-open the debate on the Font preferences dialog, but ... I
found that the new design was slightly distracting. In particular the presence
of the "Use non-TeX fonts" checkbox at the top of the list was driving me nuts.
Because of this, I took an opportuni
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
Am 17.11.2010 um 23:02 schrieb Enrico Forestieri:
> On Wed, Nov 17, 2010 at 04:19:34PM -0500, Richard Heck wrote:
>> On 11/17/2010 03:48 PM, Enrico Forestieri wrote:
>>>
>>> As regards the other isxxx() tests, I suggest to audit them on an as
>>> needed basis, according to what the posix standard
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:
> 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 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
> No, this should never be empty. We specifically push a null pointer onto the
> stack at the beginning, as a kind
> of dummy entry that makes sure we never pop more than we push. If it is
> empty, then we have popped more
> than we have pushed.
>
I don't understand why we do that. We only push&po
Enrico Forestieri wrote:
> Please, see comments below.
one related request: could you post patch for examples/instant_preview.lyx
which contains working example for tikz and example for pstrick?
we should distribute it as well.
pavel
On Thu, Dec 02, 2010 at 10:51:45AM +0100, veno...@arcadiaclub.com wrote:
> OK, I've patched lyxpreview2bitmap.py, take a look at the attached file and
> tell
> me if it works for you. I've attached also some test LaTeX files I've tested.
> It seems we've reached a very good solution, I'm really s
On Thu, Dec 2, 2010 at 4:48 PM, Jean-Marc Lasgouttes wrote:
> Le 2 déc. 2010 à 16:19, Richard Heck a écrit :
>> The point here is that the old line completely wipes out the counters,
>> including all record of which counters
>> there are but, in this case, most importantly, it doesn't reset the
Le 2 déc. 2010 à 16:19, Richard Heck a écrit :
> The point here is that the old line completely wipes out the counters,
> including all record of which counters
> there are but, in this case, most importantly, it doesn't reset the
> layout_stack_.
You hid a layout stack in counters? That looks b
On 12/02/2010 10:14 AM, rgh...@lyx.org wrote:
Author: rgheck
Date: Thu Dec 2 16:14:44 2010
New Revision: 36657
URL: http://www.lyx.org/trac/changeset/36657
Log:
Fix crash reported by keytest.
Modified:
lyx-devel/trunk/src/insets/InsetText.cpp
Modified: lyx-devel/trunk/src/insets/InsetText
On 12/02/2010 08:43 AM, John McCabe-Dansted wrote:
Keycodes:
'''\Af\C\[Left]\Am\Av\Af\Ay'''\[!Loop]\Af
To reproduce:
1) Press Alt-H, M to open the Math Guide. (KK: \Af) (KK: \C\[Left]) (KK: \Am)
2) Press Alt-V, F, Y to view LyXHTML (KK: \Av\Af\Ay)
Regression in: r36603
Fixed ar r36657.
Rich
On 12/02/2010 09:04 AM, Vincent van Ravesteijn wrote:
On Thu, Dec 2, 2010 at 2:43 PM, John McCabe-Dansted wrote:
Keycodes:
'''\Af\C\[Left]\Am\Av\Af\Ay'''\[!Loop]\Af
To reproduce:
1) Press Alt-H, M to open the Math Guide. (KK: \Af) (KK: \C\[Left]) (KK: \Am)
2) Press Alt-V, F, Y to view LyXHTML
Jean-Marc Lasgouttes wrote:
> We should really have a strict policy for new hardcoding, i.e. make it
> forbidden
> by default.
it would be enough if patches are discuscussed before committed.
yes, i'm repetitive but what can i do ;)
for this moment i will ask for revert.
pavel
Le 2 déc. 2010 à 15:29, Vincent van Ravesteijn a écrit :
We should really have a strict policy for new hardcoding, i.e. make it forbidden
>> by default.
>>
>
> Yes, you mean we can clear up half of the src/insets/*.cpp code if we
> use layouts and generalisation more.
Agreed, but this is not wha
> We should really have a strict policy for new hardcoding, i.e. make it
> forbidden
> by default.
>
Yes, you mean we can clear up half of the src/insets/*.cpp code if we
use layouts and generalisation more.
Vincent
Le 2 déc. 2010 à 15:11, Pavel Sanda a écrit :
> ugh. instead of hardcoding such hacks we should go for date inside
> insetinfo...
Yes, or have date use a fancy python script.
We should really have a strict policy for new hardcoding, i.e. make it forbidden
by default.
JMarc
On Thu, Dec 2, 2010 at 10:04 PM, Vincent van Ravesteijn wrote:
> On Thu, Dec 2, 2010 at 2:43 PM, John McCabe-Dansted wrote:
>> Keycodes:
>> '''\Af\C\[Left]\Am\Av\Af\Ay'''\[!Loop]\Af
>> To reproduce:
>> 1) Press Alt-H, M to open the Math Guide. (KK: \Af) (KK: \C\[Left]) (KK:
>> \Am)
>> 2) Press
uwesto...@lyx.org wrote:
> Author: uwestoehr
> Date: Thu Dec 2 05:05:35 2010
> New Revision: 36654
> URL: http://www.lyx.org/trac/changeset/36654
>
> Log:
> ExternalSupport.cpp: fix #4398 (omit the newline in the LaTeX output behind
> the ExternalInset inset if the inset type is a date)
>
> Mod
On 02/12/2010 4:51 AM, veno...@arcadiaclub.com wrote:
OK, I've patched lyxpreview2bitmap.py, take a look at the attached file and tell
me if it works for you. I've attached also some test LaTeX files I've tested.
It seems we've reached a very good solution, I'm really satisfied. Now we need
some
Uwe Stöhr wrote:
>> Uwe, do you know how to kill the useless spaces between individual lfuns
>> in the printed manual?
>> Your transformation from ams related class still gives superfluous +10
>> pages...
>
> I don't understand. I haven't touched LFUNS.lyx. The PDF output of the
http://www.mail
On Thu, Dec 2, 2010 at 2:43 PM, John McCabe-Dansted wrote:
> Keycodes:
> '''\Af\C\[Left]\Am\Av\Af\Ay'''\[!Loop]\Af
> To reproduce:
> 1) Press Alt-H, M to open the Math Guide. (KK: \Af) (KK: \C\[Left]) (KK: \Am)
> 2) Press Alt-V, F, Y to view LyXHTML (KK: \Av\Af\Ay)
>
> Regression in: r36603
>
I
Keycodes:
'''\Af\C\[Left]\Am\Av\Af\Ay'''\[!Loop]\Af
To reproduce:
1) Press Alt-H, M to open the Math Guide. (KK: \Af) (KK: \C\[Left]) (KK: \Am)
2) Press Alt-V, F, Y to view LyXHTML (KK: \Av\Af\Ay)
Regression in: r36603
Arch: x86_64
Revision: 36644
{{{
lassert.cpp(21): ASSERTION !layout_stack_.
OK, I've patched lyxpreview2bitmap.py, take a look at the attached file and tell
me if it works for you. I've attached also some test LaTeX files I've tested.
It seems we've reached a very good solution, I'm really satisfied. Now we need
some testing.
venom00
detect_specials.diff
Description: Bi
Am 02.12.2010 um 03:53 schrieb Pavel Sanda:
> Stephan Witt wrote:
>>> I've a personal dictionary solution for hunspell ready.
>>
>> This is the patch for having a personal word list with hunspell.
>> It makes "Add to personal dictionary" and "Remove from personal dictionary"
>> working.
>>
>> I
72 matches
Mail list logo
