Am Montag, 14. Januar 2013 um 09:45:11, schrieb Nico Williams
> On Sun, Jan 13, 2013 at 7:18 AM, Kornel Benko wrote:
> >> Also, does this cmake command pollute my source tree? How can I define a
> >> build tree?
> >
> > I tried to pollute as little as possible, but in general, you are not
> > en
On Jan 13, 2013, at 8:25 PM, Jerry wrote:
>
> On Jan 13, 2013, at 6:49 AM, Stephan Witt wrote:
>
>> Am 13.01.2013 um 14:18 schrieb Kornel Benko :
>>
>>> Am Samstag, 12. Januar 2013 um 19:24:32, schrieb Jerry
>>>
Back on the bisection trail
I'm having more trouble building
On 12/01/2013 11:34 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
The goal is to translate these strings (using mo database) to the
document language.
Then Buffer::B_() is the correct approach.
Jürgen
Does something like the attached patch (for branch) look OK?
Regards,
Julien
>From a
On 13-Jan-13 6:10 PM, Uwe Stöhr wrote:
Am
13.01.2013 07:13, schrieb Zohar Levi:
I apologize for my rudeness. Sometimes
when someone doesn't listen, and I need
to repeat myself three times, I lose control, even if he has the
On Mon, Jan 14, 2013 at 1:10 PM, Jerry wrote:
> If you are implying complete automation, I have no idea how to make a script
> that scrolls through the User's Guide (my objective test) and measures how
> long it takes.
No, you have to do that part yourself. Well, there are UI macro type
tools
On Jan 14, 2013, at 8:45 AM, Nico Williams wrote:
> On Sun, Jan 13, 2013 at 7:18 AM, Kornel Benko wrote:
>>> Also, does this cmake command pollute my source tree? How can I define a
>>> build tree?
>>
>> I tried to pollute as little as possible, but in general, you are not
>> encouraged to call
On Sun, Jan 13, 2013 at 7:18 AM, Kornel Benko wrote:
>> Also, does this cmake command pollute my source tree? How can I define a
>> build tree?
>
> I tried to pollute as little as possible, but in general, you are not
> encouraged to call
>
> cmake from the source tree.
You can always git clean.
On 2013-01-14, Enrico Forestieri wrote:
> On Mon, Jan 14, 2013 at 02:33:36AM +0100, Uwe Stöhr wrote:
>> But to come to an end, decide once again but please act then
>> consistently. I will have to update IEEEtran and I want to know from
>> you what I should do now.
> Nothing. If you do nothing, y
Hello Uwe
On Mon, Jan 14, 2013 at 2:33 AM, Uwe Stöhr wrote:
>> The Windows installer is your business.
>
> That is not fair. We can assume that at least 50% of our users use LyX on
> Windows.
>
This is harsh reasoning. In many cases open-source projects only take
responsibility for providing sou
On 2013-01-14, Uwe Stöhr wrote:
> Am 02.01.2013 15:42, schrieb Richard Heck:
> I want:
> - for paper submission classes we can change the layout for every LyX
> release (this might break backward compatibility but for these
> classes you are not allowed to use older class versions)
> - for no
On Mon, Jan 14, 2013 at 02:33:36AM +0100, Uwe Stöhr wrote:
> But to come to an end, decide once again but please act then
> consistently. I will have to update IEEEtran and I want to know from
> you what I should do now.
Nothing. If you do nothing, you break nothing.
http://www.lyx.org/trac/tick
Wolfgang Engelmann wrote:
> I took out all lines from the preamble except
> \usepackage{cite}
> but still no change.
>
> Any idea what goes wrong?
Did you put the citations that have to be compressed into _one_ citation
inset? This is necessary.
If you do so, we need a minimal example file.
12 matches
Mail list logo
