Am 02.11.2010 um 07:31 schrieb Stephan Witt:
> Am 01.11.2010 um 23:42 schrieb Pavel Sanda:
>
>> Stephan Witt wrote:
>>
>>> 3) Want the readFile() issue fixed.
>>
>> is this beta1 critical stuf?
>
> After my last commit in readFile() it's "only" the issue with file_found_hook
> being called w
Am 01.11.2010 um 23:42 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Sorry, I went out and could not answer :-)
>>
>> 1) I have a patch at hand to add the ability to collect stderr in system call
>> and to simplify the stdout collection too. This patch doesn't change the
>> current interface but
On 01/11/2010 6:49 PM, Pavel Sanda wrote:
Julien Rioux wrote:
This is with instant preview on, opening the file examples/lilypond.lyx,
the preview fails (some lilypond code in there should be changed) and then
this signal occurs.
thanks, can you try whether trunk, r35921 is better,
because my
thanks, can you try whether trunk, r35921 is better,
because my guess to the r35922 ... ?
No in fact backtrace is almost identical:
latex failed to compile 0lyxpreview.tex
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
restricted \write18 enabled.
entering extended mode
(./0l
Julien Rioux wrote:
> This is with instant preview on, opening the file examples/lilypond.lyx,
> the preview fails (some lilypond code in there should be changed) and then
> this signal occurs.
thanks, can you try whether trunk, r35921 is better,
because my guess to the r35922 ... ?
pavel
Stephan Witt wrote:
> Sorry, I went out and could not answer :-)
>
> 1) I have a patch at hand to add the ability to collect stderr in system call
> and to simplify the stdout collection too. This patch doesn't change the
> current interface but adds a second one. VCS is more clean with that.
> Th
This is with instant preview on, opening the file examples/lilypond.lyx,
the preview fails (some lilypond code in there should be changed) and
then this signal occurs.
I'm on ubuntu 10.10, qt 4.7.0, tr...@r35984
latex failed to compile 0lyxpreview.tex
This is pdfTeX, Version 3.1415926-1.40.10
Am 01.11.2010 um 16:48 schrieb Pavel Sanda:
> Richard Heck wrote:
>> On 11/01/2010 09:20 AM, Pavel Sanda wrote:
>>> hi,
>>>
>>> 1. Richard, whats the status of a)? i'm basically waiting only for this.
>>> could you give it top priority on your list if its not fixed yet?
>>>
>>>
>> Will do.
>
>
Richard Heck wrote:
>
> Could that be removed? Does anyone use it any more? Even xdvi seems to
> detect paper size and such nowadays.
>
> The point of removing it is that then Formats::view() would not really need
> a Buffer argument. The message we write doesn't last, anyway, especially
> with
On 11/01/2010 11:22 AM, Pavel Sanda wrote:
Richard Heck wrote:
On 11/01/2010 09:54 AM, Pavel Sanda wrote:
Richard Heck wrote:
So, here is the current status.
do you think its worth to add it even in the current status?
We can't fix the problem with sec
I would like to do backtrace, but have not done this before. Do I need to
compile with special flags?
yes, ./configure --enable-debug&& make
then gdb src/lyx
and after crash type 'bt' in console and post the result here.
Better yet: --enable-build-type=-dev
rh
Julien Rioux wrote:
> No it didn't crash before, but I did svn up since the last time I edited
> that file.
there has been some movement in instant preview code last days :)
> I would like to do backtrace, but have not done this before. Do I need to
> compile with special flags?
yes, ./configu
On 01/11/2010 5:08 PM, Pavel Sanda wrote:
Julien Rioux wrote:
I have a patch coming, I also wanted to update the documentation a bit, but
at the moment I got a SIGSEGV when opening the examples/lilypond.lyx file
with tr...@r35964
did it crash before?
i dont see it here, but i dont have lilypon
Julien Rioux wrote:
> Lilypond 2.13 is devel-only, not a public release (all their odd version
> numbers are devel-only) so I don't think we need to bother with a check on
> 2.13.8. Version 2.14 is the next public release.
thanks for info, closing the bug.
nice contribution btw.
pavel
On 01/11/2010 5:05 PM, Pavel Sanda wrote:
sa...@lyx.org wrote:
Author: sanda
Date: Mon Nov 1 22:01:48 2010
New Revision: 35978
URL: http://www.lyx.org/trac/changeset/35978
Log:
Fix lilypond support, patch from Julien Rioux, bug #6940.
Modified:
lyx-devel/trunk/lib/configure.py
lyx-dev
Julien Rioux wrote:
> I have a patch coming, I also wanted to update the documentation a bit, but
> at the moment I got a SIGSEGV when opening the examples/lilypond.lyx file
> with tr...@r35964
did it crash before?
i dont see it here, but i dont have lilypond installed and thus no instant
previ
sa...@lyx.org wrote:
> Author: sanda
> Date: Mon Nov 1 22:01:48 2010
> New Revision: 35978
> URL: http://www.lyx.org/trac/changeset/35978
>
> Log:
> Fix lilypond support, patch from Julien Rioux, bug #6940.
>
> Modified:
>lyx-devel/trunk/lib/configure.py
>lyx-devel/trunk/lib/scripts/lyxp
Julien Rioux wrote:
> Can someone upload this file to wiki please?
> or
> What's the wiki upload password?
sent privately
pavel
On 11/01/2010 02:26 PM, Pavel Sanda wrote:
i consider this bug to be urgent: #6809
but this can be done by more people. the fullscreen menu was your area of
expertise.
I don't see this bug now.
rh
I've attached a patch to the issue. It deals with the calls to lilypond
and make them safe. I'll add some documentation once I can use lyx
without crash!
--
Julien
I have a patch coming, I also wanted to update the documentation a bit,
but at the moment I got a SIGSEGV when opening the examples/lilypond.lyx
file with tr...@r35964
On 01/11/2010 3:25 PM, LyX Ticket Tracker wrote:
#6940: Check lilypond before release
-+--
On 01/11/2010 19:26, Pavel Sanda wrote:
Abdelrazak Younes wrote:
At least I know I
can fix things in case I break them.
i'm happy to hear this :))
please on the top of the splitting issues, can you have look on imho
related bugs 6896, 6453?
I really don't see the lik be
Abdelrazak Younes wrote:
>>> At least I know I
>>> can fix things in case I break them.
>>>
>> i'm happy to hear this :))
>> please on the top of the splitting issues, can you have look on imho
>> related bugs 6896, 6453?
>>
>
> I really don't see the lik between r34054 and these two bug
On 01/11/2010 19:15, Uwe Stöhr wrote:
Am 01.11.2010 18:19, schrieb Abdelrazak Younes:
Did I respond?
Not yet ;-)
The problem in #6997 is not a general issue, it is just a problem
with the table dialog because we
don't read the full table parameters each time we move. So that is a
bug and i
Am 01.11.2010 18:19, schrieb Abdelrazak Younes:
Did I respond?
Not yet ;-)
The problem in #6997 is not a general issue, it is just a problem with the
table dialog because we
don't read the full table parameters each time we move. So that is a bug and it
is fixable. But as
Juergen said else
On 01/11/2010 18:36, Pavel Sanda wrote:
Abdelrazak Younes wrote:
At least I know I
can fix things in case I break them.
i'm happy to hear this :))
please on the top of the splitting issues, can you have look on imho related
bugs 6896, 6453?
I really don't see the lik between r3
Abdelrazak Younes wrote:
> At least I know I
> can fix things in case I break them.
i'm happy to hear this :))
please on the top of the splitting issues, can you have look on imho related
bugs 6896, 6453?
i guess its not new breakage but rather unfinished menu displaying code...
>I can stop thi
On 01/11/2010 14:46, Pavel Sanda wrote:
Richard Heck wrote:
I don't understand the split screen stuff, so I'm not sure why this would
only happen then. But here's a simple recipe to reproduce.
which reminds me - Abdel please can you have finally look at the #34054?
there seems to
On 01/11/2010 03:10, Uwe Stöhr wrote:
Am 01.11.2010 02:19, schrieb Vincent van Ravesteijn:
> However, you introduced a new feature, multirows, and then report bug
> #6985, #6958, #6999 and then you see that you don't like the apply
> scheme and you report bug #6998, #6997, #7001 and then also bu
On 31/10/2010 19:56, rgh...@lyx.org wrote:
Author: rgheck
Date: Sun Oct 31 19:56:32 2010
New Revision: 35952
URL: http://www.lyx.org/trac/changeset/35952
Log:
Revert r35933. There are insets not based upon InsetCommand, such as
VSpace, that use InsetParamsWidget, so we cannot have code that requ
On 31/10/2010 23:08, Uwe Stöhr wrote:
No, but note that if we do not manage to solve the tabular issues with
multirow before 2.0 (which is not unlikely), I will vote for
deactivating
multirow support. We cannot ship a defect feature.
I'm not responsible for the new tabular Apply/OK scheme. A
On 31/10/2010 17:10, Uwe Stöhr wrote:
Am 31.10.2010 16:07, schrieb Jürgen Spitzmüller:
The only issue I see right now is that one cannot set a multirow via
the
dialog What else do you see that is not yet also in LyX 1.6.x?
Yes, but this issue is quite tricky. I'm not even sure it is solvabl
Uwe Stöhr a écrit :
I haven't followed this thread, but have you seen that the new version
0.4 of refstyle supports now French:
http://article.gmane.org/gmane.comp.tex.ctan.announce/8109
Sure, this follows a private mail exchange with Danie Els.
--
Jean-Pierre
Am Montag 01 November 2010 schrieb Pavel Sanda:
> Kornel Benko wrote:
> > > The nicest solution could be the attached patch.
> >
> > +1
>
> i really dont believe thats not possible to use some kind of slovak version
> of "neni k dispozici" as a single string.
This would be ok. All other possible
tephan Witt wrote:
> I'd code the invers operation for getEmergencyFileNameFor() and
> getAutosaveFileNameFor().
> Then I'd use the result in readFile() to pass to file_found_hook().
>
> The other possibility I can see is to pass the original filename as optional
> argument.
for sure Vincent wi
Kornel Benko wrote:
> > The nicest solution could be the attached patch.
>
> +1
i really dont believe thats not possible to use some kind of slovak version of
"neni k dispozici" as a single string.
pavel
Stephan Witt wrote:
> In the current state of buffer read the vcs info inset output is broken.
well, looking now its not only insetinfo but the whole vcs which is broken,
just try to look on the toolbar when loading lyx file under svn. perhaps
last refactorization on loading hierarchy ;)
so any q
Am Montag 01 November 2010 schrieb Stephan Witt:
> Am 01.11.2010 um 16:18 schrieb Pavel Sanda:
> > Kornel Benko wrote:
> >> Well, this is exactly the case here, as "%1$s" may have different gender
> >> in slovak for values like "vcs-revision" and "vcs-author". And I am
> >> acting as some translato
Stephan Witt wrote:
> But as said already that requires the translators to translate 5 strings...
no, one "not available" string is just enough.
pavel
Richard Heck wrote:
> On 11/01/2010 09:20 AM, Pavel Sanda wrote:
>> hi,
>>
>> 1. Richard, whats the status of a)? i'm basically waiting only for this.
>> could you give it top priority on your list if its not fixed yet?
>>
>>
> Will do.
great.
anybody around having something more to be push i
So the crash John reported comes in at r31203. Here's the recipe, again:
1. Open LyX. File>New. Document>Outline, to make sure the TOC is open.
That isn't necessary, but it helps you to see what is happening.
2. Create a section heading (alt-P, 2) with an x in it.
3. Split the screen.
4. File>
Gregory Jefferis wrote:
> looks like it has
> addressed my concern.
good news, thanks
pavel
Am 01.11.2010 um 16:18 schrieb Pavel Sanda:
> Kornel Benko wrote:
>> Well, this is exactly the case here, as "%1$s" may have different gender in
>> slovak for
>> values like "vcs-revision" and "vcs-author". And I am acting as some
>> translator here too.
>
> i understand, but inventing some mac
Richard Heck wrote:
>> yes, i'm aware of it. do you propose some alternative?
>>
>>
> I had the idea to look for a browser and record that separately. But it
> wouldn't fit into the normal "viewer" stuff.
i see. you have my ok for both alternatives - disabling it or rework
the stuff. the secu
Richard Heck wrote:
> On 11/01/2010 09:54 AM, Pavel Sanda wrote:
>> Richard Heck wrote:
>>
>>> So, here is the current status.
>>>
>> do you think its worth to add it even in the current status?
>>
>>
> We can't fix the problem with sectioned bibs. I tried, and it's intrinsic
> to ho
Kornel Benko wrote:
> Well, this is exactly the case here, as "%1$s" may have different gender in
> slovak for
> values like "vcs-revision" and "vcs-author". And I am acting as some
> translator here too.
i understand, but inventing some machinery for this corner case is really
overkill.
pavel
Am 01.11.2010 um 15:58 schrieb Pavel Sanda:
> Stephan Witt wrote:
>>> Stephan Witt wrote:
setText(_("Unknown buffer info"));
to
setText(bformat(_("[[%1$s unknown]]"), from_utf8(name_)));
setText(bformat(_("%1$s unknown[[BufferInfo]]"), from_utf8(name_)));
seems more
Stephan Witt wrote:
> > Yes, but then why not the full sentence?
> > docstring fmt = _("vcs-revision unknown")
> > We need to know what is "unknown" to translate the sentence corectly anyway.
>
> There is no sentence to translate.
we can use "not available."
pavel
On 11/01/2010 09:54 AM, Pavel Sanda wrote:
Richard Heck wrote:
So, here is the current status.
do you think its worth to add it even in the current status?
We can't fix the problem with sectioned bibs. I tried, and it's
intrinsic to how they work. (The bbl contains ALL reference
Am Montag 01 November 2010 schrieb Pavel Sanda:
> Kornel Benko wrote:
> > For instance "%1$s unknown[[vcs-author]]"
> > as that gives a hint to author. In some languages "unknown" depends also
> > on gender of "vcs-author"
>
> well it can give a hint but we dont use it for that. the basic purpose
On 11/01/2010 10:21 AM, Pavel Sanda wrote:
Richard Heck wrote:
Pavel, I think you introduced this in connection with
InsetHyperlink::viewTarget(). But it seems wrong to me. There's no
particular reason to think that the URL in that case will actually be of
type HTML, or that the viewer defin
Kornel Benko wrote:
> For instance "%1$s unknown[[vcs-author]]"
> as that gives a hint to author. In some languages "unknown" depends also on
> gender of "vcs-author"
well it can give a hint but we dont use it for that. the basic purpose is to
distinguish identical strings for a different context
Am 01.11.2010 um 15:49 schrieb Pavel Sanda:
> sw...@lyx.org wrote:
>> Author: switt
>> Date: Sat Oct 30 22:05:55 2010
>> New Revision: 35937
>> URL: http://www.lyx.org/trac/changeset/35937
>>
>> Log:
>> after successfuly load of autosave or emergency file the VCS state has to be
>> checked for t
Stephan Witt wrote:
> > Stephan Witt wrote:
> >> setText(_("Unknown buffer info"));
> >> to
> >> setText(bformat(_("[[%1$s unknown]]"), from_utf8(name_)));
> >>
> >> setText(bformat(_("%1$s unknown[[BufferInfo]]"), from_utf8(name_)));
> >> seems more correct then.
> >
> > why to put [[BufferInfo]
sw...@lyx.org wrote:
> Author: switt
> Date: Sat Oct 30 22:05:55 2010
> New Revision: 35937
> URL: http://www.lyx.org/trac/changeset/35937
>
> Log:
> after successfuly load of autosave or emergency file the VCS state has to be
> checked for the original name
i find disseminating of file_found_ho
Am 01.11.2010 um 15:34 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> setText(_("Unknown buffer info"));
>> to
>> setText(bformat(_("[[%1$s unknown]]"), from_utf8(name_)));
>>
>> setText(bformat(_("%1$s unknown[[BufferInfo]]"), from_utf8(name_)));
>> seems more correct then.
>
> why to put [[Buff
Vincent van Ravesteijn wrote:
> So, wouldn't it be logical that you first try to fix the multirow bugs
> and possibly the multicolumn bugs such that they work properly, then
> get the dialog to work before extending the multirow feature anymore,
> and introducing more ui in the table dialog, which
Am 01.11.2010 um 15:21 schrieb Kornel Benko:
> Am Montag 01 November 2010 schrieb Stephan Witt:
>> Am 01.11.2010 um 11:07 schrieb Kornel Benko:
>>> Am Montag, 1. November 2010 schrieb Stephan Witt:
Am 01.11.2010 um 07:41 schrieb Vincent van Ravesteijn:
>> + if (binfo.empty()
Stephan Witt wrote:
> setText(_("Unknown buffer info"));
> to
> setText(bformat(_("[[%1$s unknown]]"), from_utf8(name_)));
>
> setText(bformat(_("%1$s unknown[[BufferInfo]]"), from_utf8(name_)));
> seems more correct then.
why to put [[BufferInfo]] there?
pavel
Hi Pavel et al.,
On 2010-01-11 13:20, "Pavel Sanda" wrote:
> 3. Gregory, you didn't replied to us. you have only very limited time frame
>to do so, otherwise things in 2.0 might by undesirable for you.
>
>
>
>> short resume for things we need before releasing beta
>> a) - Richard has some
Richard Heck wrote:
> Pavel, I think you introduced this in connection with
> InsetHyperlink::viewTarget(). But it seems wrong to me. There's no
> particular reason to think that the URL in that case will actually be of
> type HTML, or that the viewer defined for HTML will be able to handle it.
Am Montag 01 November 2010 schrieb Stephan Witt:
> Am 01.11.2010 um 11:07 schrieb Kornel Benko:
> > Am Montag, 1. November 2010 schrieb Stephan Witt:
> >> Am 01.11.2010 um 07:41 schrieb Vincent van Ravesteijn:
> + if (binfo.empty()) {
> + docstring fmt
On 01/11/2010 9:02 AM, Yann Disser wrote:
On 1. Nov 2010, at 14:42, Jürgen Spitzmüller wrote:
Yann Disser wrote:
I wish I had time to help you with that (sounds like fun ;-) )... Perhaps
sometime in the future.
Don't count on it. We have many reasons for not using the tex file format
native
On Mon, Nov 1, 2010 at 8:56 PM, Vincent van Ravesteijn wrote:
> A slightly simpler problem is to allow users to modify the generated
> preamble. Sort of the same problem, but simpler and useful as well.
I use the attached lyxpp.py.
To use
0) Put lyxpp.py in the path.
1) Set the LaTeX (pdflatex)
Richard Heck wrote:
>
> So, here is the current status.
do you think its worth to add it even in the current status?
pavel
Richard Heck wrote:
>>> I don't understand the split screen stuff, so I'm not sure why this would
>>> only happen then. But here's a simple recipe to reproduce.
which reminds me - Abdel please can you have finally look at the #34054?
there seems to be more related bugs.
pavel
>>> 1. Open LyX. C
On 11/01/2010 09:16 AM, Yann Disser wrote:
On 1. Nov 2010, at 14:09, Pavel Sanda wrote:
Yann Disser wrote:
Your arguments make sense. However, I think many people must have my problem.
Perhaps it would be sufficient to provide a way to keep the .lyx file and the
.tex file in sync.
On 11/01/2010 09:16 AM, Yann Disser wrote:
On 1. Nov 2010, at 14:09, Pavel Sanda wrote:
Yann Disser wrote:
Your arguments make sense. However, I think many people must have my problem.
Perhaps it would be sufficient to provide a way to keep the .lyx file and the
.tex file in sync.
On 11/01/2010 09:20 AM, Pavel Sanda wrote:
hi,
1. Richard, whats the status of a)? i'm basically waiting only for this.
could you give it top priority on your list if its not fixed yet?
Will do.
rh
you...@lyx.org wrote:
> Modified: lyx-devel/trunk/src/frontends/qt4/ui/HyperlinkUi.ui
> ==
> --- lyx-devel/trunk/src/frontends/qt4/ui/HyperlinkUi.ui Wed Oct 27
> 14:55:57 2010(r35866)
> +++ lyx-devel/trunk/sr
Yann Disser wrote:
> Your arguments make sense. However, I think many people must have my
> problem. Perhaps it would be sufficient to provide a way to keep the .lyx
> file and the .tex file in sync. Whenever one of the two would get changed,
> lyx would automatically import/export. This approach w
hi,
1. Richard, whats the status of a)? i'm basically waiting only for this.
could you give it top priority on your list if its not fixed yet?
2. Vincent could you put in the pending patch for b?
3. Gregory, you didn't replied to us. you have only very limited time frame
to do so, otherwise t
On 1. Nov 2010, at 14:09, Pavel Sanda wrote:
> Yann Disser wrote:
>> Your arguments make sense. However, I think many people must have my
>> problem. Perhaps it would be sufficient to provide a way to keep the .lyx
>> file and the .tex file in sync. Whenever one of the two would get changed,
>
Yann Disser wrote:
> Your arguments make sense. However, I think many people must have my problem.
> Perhaps it would be sufficient to provide a way to keep the .lyx file and the
> .tex file in sync. Whenever one of the two would get changed, lyx would
> automatically import/export. This approac
On 1. Nov 2010, at 14:42, Jürgen Spitzmüller wrote:
> Yann Disser wrote:
>> I wish I had time to help you with that (sounds like fun ;-) )... Perhaps
>> sometime in the future.
>
> Don't count on it. We have many reasons for not using the tex file format
> natively. For instance, LyX is storin
On 11/01/2010 08:20 AM, Richard Heck wrote:
On 11/01/2010 08:14 AM, Richard Heck wrote:
On 11/01/2010 03:32 AM, John McCabe-Dansted wrote:
On Mon, Nov 1, 2010 at 1:09 PM, Vincent van Ravesteijn
wrote:
On Wed, Oct 27, 2010 at 4:37 PM, John
McCabe-Dansted wrote:
Hi Vincent, this appears to be
A slightly simpler problem is to allow users to modify the generated
preamble. Sort of the same problem, but simpler and useful as well.
Op 1 nov 2010 13:39 schreef "Yann Disser" :
On 1. Nov 2010, at 13:19, Richard Heck wrote:
> On 11/01/2010 07:56 AM, Yann Disser wrote:
>>
>> ...
I wish I had
Yann Disser wrote:
> I wish I had time to help you with that (sounds like fun ;-) )... Perhaps
> sometime in the future.
Don't count on it. We have many reasons for not using the tex file format
natively. For instance, LyX is storing some information for which no tex
syntax exists (and which do
On 1. Nov 2010, at 13:19, Richard Heck wrote:
> On 11/01/2010 07:56 AM, Yann Disser wrote:
>>
>> Thanks for your reply. I am sorry for duplicating a feature request, I did
>> not take the time to look through existing ones...
>>
> Not a problem. I just meant it wasn't something we'd overlooked
On 11/01/2010 08:14 AM, Richard Heck wrote:
On 11/01/2010 03:32 AM, John McCabe-Dansted wrote:
On Mon, Nov 1, 2010 at 1:09 PM, Vincent van Ravesteijn
wrote:
On Wed, Oct 27, 2010 at 4:37 PM, John
McCabe-Dansted wrote:
Hi Vincent, this appears to be another recent regression, this time
from r3
On 11/01/2010 07:56 AM, Yann Disser wrote:
Thanks for your reply. I am sorry for duplicating a feature request, I
did not take the time to look through existing ones...
Not a problem. I just meant it wasn't something we'd overlooked.
I hope that eventually somebody will implement it, though
On 11/01/2010 03:32 AM, John McCabe-Dansted wrote:
On Mon, Nov 1, 2010 at 1:09 PM, Vincent van Ravesteijn wrote:
On Wed, Oct 27, 2010 at 4:37 PM, John McCabe-Dansted wrote:
Hi Vincent, this appears to be another recent regression, this time
from r35832 on Monday.
Sorry John
I'm going to forward this to the devel list, as I think people there are
more likely to know about this.
rh
Original Message
Subject:Unicode help
Date: Mon, 1 Nov 2010 11:25:41 +0700
From: Daron Wilson
To: lyx-us...@lists.lyx.org
Hi all.
I've recently st
On 11/01/2010 05:38 AM, Yann Disser wrote:
Hi everybody.
I do not know where to post a feature request, so I send it to this list --
hope that's ok.
I use LyX every day at work (doing my PhD), and I am really really happy with
it!
There is one thing I am missing though, since I collaborate a
On 1. Nov 2010, at 12:51, Richard Heck wrote:
> On 11/01/2010 05:38 AM, Yann Disser wrote:
>> Hi everybody.
>>
>> I do not know where to post a feature request, so I send it to this list --
>> hope that's ok.
>>
>> I use LyX every day at work (doing my PhD), and I am really really happy
>> wit
Am 01.11.2010 um 11:07 schrieb Kornel Benko:
> Am Montag, 1. November 2010 schrieb Stephan Witt:
>> Am 01.11.2010 um 07:41 schrieb Vincent van Ravesteijn:
>>
+ if (binfo.empty()) {
+ docstring fmt = _("%1$s unknown[[InsetNote]]");
+
Am Montag, 1. November 2010 schrieb Stephan Witt:
> Am 01.11.2010 um 07:41 schrieb Vincent van Ravesteijn:
>
> >> + if (binfo.empty()) {
> >> + docstring fmt = _("%1$s unknown[[InsetNote]]");
> >> + setText(bformat(fmt, from_utf8(name_)));
In the current state of buffer read the vcs info inset output is broken.
The attached patch helps. Ok to apply?
But, there is one problem left.
When reading the autosave or emergency file the "wrong" pathname is passed to
lyxvc().file_found_hook().
That's why the additional calls I introduced in
Hi everybody.
I do not know where to post a feature request, so I send it to this list --
hope that's ok.
I use LyX every day at work (doing my PhD), and I am really really happy with
it!
There is one thing I am missing though, since I collaborate a lot with people
that I cannot convince to u
On Mon, Nov 1, 2010 at 1:09 PM, Vincent van Ravesteijn wrote:
> On Wed, Oct 27, 2010 at 4:37 PM, John McCabe-Dansted wrote:
>> Hi Vincent, this appears to be another recent regression, this time
>> from r35832 on Monday.
>
> Sorry John, your system is a bit off. I can reproduce with r35831 too ;)
Am 01.11.2010 um 07:41 schrieb Vincent van Ravesteijn:
>> + if (binfo.empty()) {
>> + docstring fmt = _("%1$s unknown[[InsetNote]]");
>> + setText(bformat(fmt, from_utf8(name_)));
>> + } else
>
> InsetNote ?
Sorry. Should be
91 matches
Mail list logo
