Enrico Forestieri wrote:
> Thanks. Am I allowed to commit things to development/cygwin in branch
> without asking for permission?
Generally yes, except for very large patches, that should be posted in
adavance (just for the sake of me keeping track) and immediately before a
release.
In any cas
I'll just mention that what I do is create a new master document that
has the correct branches enabled. In addition to giving the new
version of the document a new name, this is particularly useful when
there are many branches. For example the paper version may have e.g.
branches for Topic A and C
On Wed, Jul 1, 2009 at 5:32 PM, Enrico Forestieri wrote:
> Then, gcc3 is the current default in cygwin and gcc4 must be explicitly
> installed and selected as default through the alternatives mechanism,
> or used through appropriate configure variables.
Oh, I figured it was the default since that'
> I hoped there would be a solution that would avoid changing LyXFunc at all
> and just ignore() early when the key event are unknown.
Ah, probably because you want to isolate all Qt-related code within
frontends/qt4/. Here's yet another approach, at the keyPressEvent()
level:
http://www.lyx.or
On Wed, Jul 01, 2009 at 01:13:33AM -0400, Ben M. wrote:
>
> I'm excited about your changesets to trunk! Is it possible to
> automatically chmod the fonts? This would relieve a huge headache!
Is there any objections in setting the svn:executable property on
the ttf fonts?
The problem is that on
Le 1 juil. 09 à 22:02, Ben M. a écrit :
Thank you. I don't yet know proper C++ syntax, so I will do these
silly things while I learn.
No problem, I am here just for that. You are a very efficient student :)
What I would like is to drop the "Unknown function part" and only
test
on isKnown.
On Tue, Jun 30, 2009 at 08:07:25PM -0400, Ben M. wrote:
> On Tue, Jun 30, 2009 at 6:04 PM, Enrico Forestieri wrote:
> > Note that those three lines are actually what is necessary to compile
> > and install LyX provided that 1) you set the QT4DIR environment variable
> > to the directory where you i
Le 1 juil. 09 à 19:31, Edwin Leuven a écrit :
j-marc wrote:
This is not a surprise, since your files are encoded in latin1, but
there is no \usepackage[latin1]{inputenc} in there.
i am sure this comes as a surprise though to encoding ignorant
people like me.
I understand that. We have the
On Wed, Jul 01, 2009 at 10:20:30AM +0200, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
>
> > Jürgen, OK for branch?
>
> OK.
Thanks. Am I allowed to commit things to development/cygwin in branch
without asking for permission?
--
Enrico
On Wed, Jul 1, 2009 at 6:40 AM, Jean-Marc Lasgouttes wrote:
> First incident remark: use
> known = !qkey_to_string(key_).empty();
> instead.
Thank you. I don't yet know proper C++ syntax, so I will do these
silly things while I learn.
> What I would like is to drop the "Unknown function par
j-marc wrote:
> This is not a surprise, since your files are encoded in latin1, but
> there is no \usepackage[latin1]{inputenc} in there.
i am sure this comes as a surprise though to encoding ignorant people like me.
it's a (chunk of a) file from one of my students btw, and it compiles without
Helge Hafting wrote:
>> Which name (if several active branches are involved)?
>
> The names of all active branches that has this box checked. I meant to
> have one checkbox per branch.
Yes, this strikes me sensible. I first thought Jean-Marc was thinking of one
general check-box only.
Jürgen
Jürgen Spitzmüller wrote:
Jean-Marc Lasgouttes wrote:
I have to say that I use that too. What we have to do is to find the
correct, not over-engineered implementation.
+1.
The simplest would be a "add name when exporting" checkbox. That could
maybe be done by a change to Buffer::latexName.
Jean-Marc Lasgouttes wrote:
> Append all the names of the active branches which have "add name when
> exporting" selected.
Yes, that would work in most cases.
Jürgen
Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>
>> I have to say that I use that too. What we have to do is to find the
>> correct, not over-engineered implementation.
>
> +1.
>
>> The simplest would be a "add name when exporting" checkbox. That could
>> maybe be done by a change to Bu
Edwin Leuven writes:
> i get errors like these:
>
> Error 42 returned from iconv when converting from UTF-8 to UCS-4LE: Illegal
> byte
> sequence
> Converted input:
> Stopped at: 0xe9
> Unconverted input: 0x63 0x69
> Converted output:
>
> example files attached.
>
> can anyone confirm?
This is
Jean-Marc Lasgouttes wrote:
> I have to say that I use that too. What we have to do is to find the
> correct, not over-engineered implementation.
+1.
> The simplest would be a "add name when exporting" checkbox. That could
> maybe be done by a change to Buffer::latexName.
Which name (if several
Helge Hafting writes:
> It is useful to give active branches opportunity to add to the
> filename of exported files. This way, exports with and without the
> branch won't collide.
>
> My common case:
> I make a test for my students, with answers in a "answers" branch.
> When I export this to pdf,
i get errors like these:
Error 42 returned from iconv when converting from UTF-8 to UCS-4LE: Illegal byte
sequence
Converted input:
Stopped at: 0xe9
Unconverted input: 0x63 0x69
Converted output:
example files attached.
can anyone confirm?
thanks and regards, edwin
test.tex
Description: tes
It is useful to give active branches opportunity to add to the filename
of exported files. This way, exports with and without the branch won't
collide.
My common case:
I make a test for my students, with answers in a "answers" branch.
When I export this to pdf, I get "test.pdf". After activatin
"Ben M." writes:
> On Tue, Jun 30, 2009 at 5:12 AM, Jean-Marc Lasgouttes
> wrote:
>> What I would like (but I have not understood yet where to do that) is to
>> use reject() only when we have an unknown keysym. We should not reject
>> events because M-C-j is not bound currently, but because a giv
Enrico Forestieri wrote:
> Jürgen, OK for branch?
OK.
Jürgen
22 matches
Mail list logo
