Alex Fernandez wrote:
> But that is not the argument I am making. Instead, it is: this nice
> little hack solves a problem (HTML export with different tools) in the
> long term, and it does not add to the big issue (clutter in the export
> menu) significantly. The "better" solution is an overall im
Jürgen Spitzmüller wrote:
> * in configure.py, check for \viewer_alternatives and
> \converter_alternatives next to the \viewer and \converter we already
> check for. That is: the first found viewer/converter in the list
> (currently the one that is used exclusively) is stored as \viewer or
>
Could someone please update the list with 1.6.5 (or 1.6.5 svn) thanks!
/Anders
On Sat, Sep 5, 2009 at 10:57 AM, Jürgen Spitzmüller wrote:
> OK, let's try to turn this discussion to a more productive direction. Do you
> want to volunteer to help us doing it properly?
No, sorry. I really can't because of a couple of reasons:
1. Honestly, I can manage the Python part, but my C
Alex Fernandez wrote:
>1. Honestly, I can manage the Python part, but my C++ skills are
>dubious at best. I am not confident to do this kind of development.
I was in the same situation when I started LyX development (minus the Python
skills). In a sense, I still am.
> 2. I don't really think thi
On Sat, Sep 5, 2009 at 1:51 PM, Jürgen Spitzmüller wrote:
> You already said that you do not care about, e.g., CJKLyX converters. For
> others, these are crucial. Other users do not care about HTML converters,
> because they do not use it (me, for instance).
Sure, I do not care about them, but I d
Alex Fernandez wrote:
> Then you have not understood my proposal: I don't want to clutter the
> menu at all. Tell me, how many HTML converters do you currently have
> on your machine?
I think 4 or 5.
> If the answer is 0 or 1, you would get exactly the
> same entries as you already have: 0 or 1.
On 09/04/2009 07:08 PM, Tommaso Cucinotta wrote:
rgheck ha scritto:
Exactly what I was needing, thanks. I also found out that
boost/xpressive has a support for that, just checking if it works.
Does not even compile on my system :-(. Should I expect any difference
if trying with included boost ?
On 09/05/2009 08:17 AM, Alex Fernandez wrote:
Then you have not understood my proposal: I don't want to clutter the
menu at all. Tell me, how many HTML converters do you currently have
on your machine? If the answer is 0 or 1, you would get exactly the
same entries as you already have: 0 or 1. On
On 09/05/2009 07:51 AM, Jürgen Spitzmüller wrote:
Alex Fernandez wrote:
1. Honestly, I can manage the Python part, but my C++ skills are
dubious at best. I am not confident to do this kind of development.
I was in the same situation when I started LyX development (minus the Python
ski
> Result in lyx-users: 5 success, 3 failures, clearly related to the TeXLive
version (failure is
> with TeXLive 2007).
>
> I myself upgraded TeXLive to 2008 with success (without and with my patch).
OK so it is a bug in TeXLive 2007. TeXLive 2008 and MiKTeX 2.7 and 2.8 don't show the problem.
T
On Sat, Sep 5, 2009 at 3:55 PM, rgheck wrote:
> LyX currently checks for htlatex, latex2html, and hevea, and it ought also
> to check for plastex (I keep meaning to do that). I have all of these.
> Should they all be on the menu, along with elyxer?
Sure, why not. Maybe in a submenu. Otherwise why
Anders Ekberg wrote:
> Could someone please update the list with 1.6.5 (or 1.6.5 svn) thanks!
Please use 1.6.0svn for branch. We add 1.6.5 when 1.6.5 is released.
Jürgen
On 09/05/2009 10:27 AM, Alex Fernandez wrote:
On Sat, Sep 5, 2009 at 3:55 PM, rgheck wrote:
LyX currently checks for htlatex, latex2html, and hevea, and it ought also
to check for plastex (I keep meaning to do that). I have all of these.
Should they all be on the menu, along with elyxer?
On Sat, Sep 5, 2009 at 4:51 PM, rgheck wrote:
>> Sure, why not. Maybe in a submenu. Otherwise why do you have them?
>
> That would be the worry about clutter.
Thanks :) I understand the worry, I just don't share it in this
instance. Surely you can live with 4 additional entries in the Export
menu
Jürgen Spitzmüller wrote:
> > Your proposal meanwhile is "do the
> > dirty work I won't bother to do".
>
> I did not say I don't bother to implement it. I said I do not have time at
> the moment to finish what I've started. But I also proposed my help.
Never mind. I finished the viewer part mys
On 05/09/2009 17:11, Jürgen Spitzmüller wrote:
Jürgen Spitzmüller wrote:
Your proposal meanwhile is "do the
dirty work I won't bother to do".
I did not say I don't bother to implement it. I said I do not have time at
the moment to finish what I've started. But I also proposed my
On 09/05/2009 11:10 AM, Alex Fernandez wrote:
On Sat, Sep 5, 2009 at 4:51 PM, rgheck wrote:
Sure, why not. Maybe in a submenu. Otherwise why do you have them?
That would be the worry about clutter.
Thanks :) I understand the worry, I just don't share it in this instance.
S
Abdelrazak Younes wrote:
> I could have bet this will end like that ;-)
BTW, I get:
GuiApplication.cpp: In member function ‘virtual bool
lyx::frontend::GuiApplication::x11EventFilter(XEvent*)’:
GuiApplication.cpp:1641: error: ‘class
On 05/09/2009 17:20, Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
I could have bet this will end like that ;-)
BTW, I get:
GuiApplication.cpp: In member function ‘virtual bool
lyx::frontend::GuiApplication::x11EventFilter(XEvent*)’:
GuiApplication.cpp:1641: error: ‘class lyx::
On Sat, Sep 5, 2009 at 5:20 PM, rgheck wrote:
> But that is precisely the point: We're not talking about four extra entries.
> We're not going to do something special for HTML here, as much as you would
> apparently like us to do so.
Actually I was not waiting for you to do it; I was volunteering
Le 05/09/2009 20:08, Alex Fernandez a écrit :
I just don't think that principles should always trump common sense.
Or that all formats are born equal.
Indeed. I _never_ use HTML for LyX documents ;)
JMarc
On Sat, Sep 05, 2009 at 05:09:47PM +0200, you...@lyx.org wrote:
> Author: younes
> Date: Sat Sep 5 17:09:45 2009
> New Revision: 31290
> URL: http://www.lyx.org/trac/changeset/31290
>
> Log:
> * GuiView: get rid of Buffer() and documentBuffer() access.
Abdel, after this commit LyX crashes when
Enrico Forestieri schreef:
On Sat, Sep 05, 2009 at 05:09:47PM +0200, you...@lyx.org wrote:
Author: younes
Date: Sat Sep 5 17:09:45 2009
New Revision: 31290
URL: http://www.lyx.org/trac/changeset/31290
Log:
* GuiView: get rid of Buffer() and documentBuffer() access.
Abdel, after this
Christian Ridderström wrote:
>>> Isn't it a shame we can't make a master in which we include all manuals
>>> as children ?
>>
>> each manual is a fine tuned thing and have different set of preamble
>> things which are needed to compile well. i needed this for search
>> possibility through all man
Enrico Forestieri wrote:
> On Sun, Aug 23, 2009 at 11:36:21PM +0200, Uwe Stöhr wrote:
>
> > thanks for your documentation addition/update. Nevertheless your commit
> > makes it hard to keep the documentation up to date.
>
> Sorry, I will take care to not try to update the docs anymore.
>
> > Can
Hartmut Haase wrote:
> Hi Pavel,
> can we do something like the attached file with your new feature? If yes, how?
if you mean how to do the ERT
\lettrine[ante=\lglqq, loversize=0.1]{A}{ }
i have no idea how to get the '[ante=\lglqq, loversize=0.1]' part into the
output :(
the part '{A}{ }' can
Jürgen Spitzmüller wrote:
> Alex Fernandez wrote:
> > I think that requesting such a feature is wrapping the bandage before
> > you get the cut: nobody has asked for it and it is likely it will
> > never be a problem anyway. Why not create different HTML converters
> > and see if it is actually a p
Liviu Andronic wrote:
> > > A BibTeX entry for LaTeX users is
> > >
> > > @Manual{,
> > > title = {R: A Language and Environment for Statistical Computing},
> > > author = {{R Development Core Team}},
> > > organization = {R Foundation for Statistical Computing},
> > > address = {Vienna, Austria},
Jean-Marc Lasgouttes wrote:
> Some people say that good things always come to an end, but this implies
> that good things have to start at some point too. I am glad to announce the
> birth of our third child Ars?ne (who is thus a boy, for those of you who
> slept during French literature courses
Pavel Sanda schreef:
Christian Ridderström wrote:
Isn't it a shame we can't make a master in which we include all manuals
as children ?
each manual is a fine tuned thing and have different set of preamble
things which are needed to compile well. i needed this for search
possibility
Vincent van Ravesteijn wrote:
> They should be compatible.
iirc Uwe had some reason for this.
pavel
Tommaso Cucinotta wrote:
> Pavel Sanda ha scritto:
>>> On a related note, I don't know why the "C-S-f" short-cut does not
>>> appear in the menu', like it happens for the "C-f" one. Any clue ?
>>>
>> looks like a bug in our machinery. worth to report it in trac.
>>
> I'm scared it's instead
Vincent van Ravesteijn wrote:
> tomm...@lyx.org schreef:
>> Author: tommaso
>> Date: Sat Aug 22 18:16:56 2009
>> New Revision: 31203
>> URL: http://www.lyx.org/trac/changeset/31203
>>
>> Log:
>> Added at the LyXView level distinction among currently selected WorkArea
>> (and BufferView) and docume
>> Would it be possible for LyX to ship with every release an up-to-date
>> BibTeX file? It would be nice to have this information readily
>> available in LyX, and perhaps it would prompt users that LyX can and
>> probably should be cited when used.
Why is that usefule? LyX cannot really be "cite
Vincent van Ravesteijn - TNW wrote:
> http://www.tuxradar.com/content/lyx-made-easy
>
> Vincent
and some blogs
http://mozglubov.blogspot.com/2009/08/software-review-lyx.html
http://techblog.aasisvinayak.com/lyx-editor-a-powerful-editor-for-researchers/
1. new file
2. find and open (advanced) //open
3. close file
4. find and open (advanced) //close
5. kaboom
37 matches
Mail list logo
