Re: Dock status tied to documents rather than windows?

Bennett Helm wrote: On Wed, Jun 11, 2008 at 6:41 PM, Abdelrazak Younes <[EMAIL PROTECTED] > By the way, where do we store information about dock status, dialog locations, etc.? We (well, I) use Qt tools (QSettings, etc). But f

Re: Question on copiers

Georg Baum wrote: The external template mechanism was designed exactly for this purpose. With an external template the user can define a set of input files, a set of output files, a conversion command that creates the output files from the input files, and the TeX code that should be inserted i

Re: Dock status tied to documents rather than windows?

On Wed, Jun 11, 2008 at 6:41 PM, Abdelrazak Younes <[EMAIL PROTECTED]> wrote: > Bennett Helm wrote: > >> So, having ranted a bit (sorry!), let me now raise the question: how do we >> want LyX to behave? If my views here aren't shared, would it be easy to >> have >> LyX's behavior on Mac conform mo

Re: Dock status tied to documents rather than windows?

Bennett Helm wrote: So, having ranted a bit (sorry!), let me now raise the question: how do we want LyX to behave? If my views here aren't shared, would it be easy to have LyX's behavior on Mac conform more closely to Mac users' expectations in this case? The moment I put this comment on bug

Re: [Cvslog] r25171 - in /lyx-devel/trunk: configure.ac po/Makefile.in.in

On Wed, Jun 11, 2008 at 02:42:51PM +0200, Jean-Marc Lasgouttes wrote: > Pavel Sanda <[EMAIL PROTECTED]> writes: > > > Jean-Marc Lasgouttes wrote: > >> Enrico Forestieri <[EMAIL PROTECTED]> writes: > >> > >> > POTFILES.in was not distributed anymore. Without that file, no Makefile > >> > would be

Re: Question on copiers

Paul A. Rubin wrote: > Richard heck wrote: >> Paul A. Rubin wrote: >>> Before putting an enhancement suggestion into bugzilla, I need to >>> check my understanding on something. Let's say that a user inserts a >>> LaTeX macro into ERT that contains a relative path to an external >>> file. LyX fa

Dock status tied to documents rather than windows?

In 1.6, the status of various docked widgets (toolbars, view-source, view-outline) is now tied to particular windows. Thus, if you have view-source on in the second window, quit LyX, and restart, view-source will be on for the second window you open, no matter which document you open in that second

Re: [Cvslog] r25171 - in /lyx-devel/trunk: configure.ac po/Makefile.in.in

Pavel Sanda <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: >> Enrico Forestieri <[EMAIL PROTECTED]> writes: >> >> > POTFILES.in was not distributed anymore. Without that file, no Makefile >> > would be generated in the po/ directory and compilation would fail with >> > a fresh checkout

Re: [Cvslog] r25171 - in /lyx-devel/trunk: configure.ac po/Makefile.in.in

Jean-Marc Lasgouttes wrote: > Enrico Forestieri <[EMAIL PROTECTED]> writes: > > > POTFILES.in was not distributed anymore. Without that file, no Makefile > > would be generated in the po/ directory and compilation would fail with > > a fresh checkout, for example. Now I see that it is distributed

Re: [Cvslog] r25171 - in /lyx-devel/trunk: configure.ac po/Makefile.in.in

Enrico Forestieri <[EMAIL PROTECTED]> writes: > POTFILES.in was not distributed anymore. Without that file, no Makefile > would be generated in the po/ directory and compilation would fail with > a fresh checkout, for example. Now I see that it is distributed again, > so there should be no problem

Re: [PATCH] Re: Lyx 1.5.X and gcc 4.3.0

Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: >> Do I read correctly that we should apply the following patch to branch? > > Just go ahead if you think it's necessary. Done. JMarc

Re: [PATCH] Re: Lyx 1.5.X and gcc 4.3.0

Pavel Sanda <[EMAIL PROTECTED]> writes: >> I see that lyx::support::abort is not defined anymore, but that it is >> still referenced in src/client/boost.cpp. What does this mean? > > nothing, its in comment ;) It looks like grep lied to me :) JMarc

Re: [PATCH] Re: Lyx 1.5.X and gcc 4.3.0

Jean-Marc Lasgouttes wrote: > Do I read correctly that we should apply the following patch to branch? Just go ahead if you think it's necessary. Jürgen

Re: [PATCH] Re: Lyx 1.5.X and gcc 4.3.0

> I see that lyx::support::abort is not defined anymore, but that it is > still referenced in src/client/boost.cpp. What does this mean? nothing, its in comment ;) pavel

Re: [Cvslog] r25171 - in /lyx-devel/trunk: configure.ac po/Makefile.in.in

On Wed, Jun 11, 2008 at 12:14:29PM +0200, Jean-Marc Lasgouttes wrote: > Pavel Sanda <[EMAIL PROTECTED]> writes: > > >> set gettext version to 0.14.5 for now > > > > currently i see this confgiure warnings: > > config.status: WARNING: intl/Makefile.in seems to ignore the --datarootdir > > setting

[PATCH] Re: Lyx 1.5.X and gcc 4.3.0

RafałMużyło <[EMAIL PROTECTED]> writes: > Quite a while ago, I created gentoo bug 214574, which resulted in > trac changeset 24069 for lyx. However, I haven't tested that fix > back then and when I finally did, I learned, that it was incorrect. > The bug is triggered by combination of using gcc 4.

Re: [Cvslog] r25171 - in /lyx-devel/trunk: configure.ac po/Makefile.in.in

Jean-Marc Lasgouttes wrote: > Is it better now? What problems remain? yes pavel

Re: r25167 - in /lyx-devel/trunk: ABOUT-NLS autogen.sh config...

Stefan Schimanski <[EMAIL PROTECTED]> writes: > cmake is broken now by that. It seems that Abdel 'solved' the problem by removing the use of included-gettext with cmake, but I'd be interested to know what the problem was. JMarc

Re: [Cvslog] r25171 - in /lyx-devel/trunk: configure.ac po/Makefile.in.in

Pavel Sanda <[EMAIL PROTECTED]> writes: >> set gettext version to 0.14.5 for now > > currently i see this confgiure warnings: > config.status: WARNING: intl/Makefile.in seems to ignore the --datarootdir > setting > config.status: WARNING: po/Makefile.in.in seems to ignore the --datarootdir > s

Re: Monochrome and GrayScale display.

Abdelrazak Younes wrote: > But you didn't answer my question about the instant preview tag... I've missed that part. > I was reading "lib/exterrnal_templates", an idea would be to add this tag: > > Preview Off                       -> There is no way to preview this > material in LyX > Preview G

Re: Monochrome and GrayScale display.

Jürgen Spitzmüller wrote: Abdelrazak Younes wrote: Only one "Show in LyX" check box should do: - graphics will be shown as-is or after conversion to a showable format - material that contains LateX snippet will go through the instant preview mechanism. Ah, you mean the "Display" comb

Re: Monochrome and GrayScale display.

Abdelrazak Younes wrote: > Only one "Show in LyX" check box should do: > - graphics will be shown as-is or  after conversion to a  showable format > - material that contains LateX snippet will go through the instant > preview mechanism. Ah, you mean the "Display" combo. Yes, that should disappear,

Re: Monochrome and GrayScale display.

Jürgen Spitzmüller wrote: Abdelrazak Younes wrote: Do you know if there is any way to know from the template if the inset is going to benefit from instant preview? Don't think so. OK. I would like to avoid putting a checkbox for that. Why? Even if a given inset can be

Re: Monochrome and GrayScale display.

Abdelrazak Younes wrote: > Do you know if there is any way to know from the template if the inset > is going to benefit from instant preview? Don't think so. > I would like to avoid putting a checkbox for that. Why? Even if a given inset can be previewed, some people might want to switch the p

Re: Monochrome and GrayScale display.

Jürgen Spitzmüller wrote: Abdelrazak Younes wrote: http://www.lyx.org/~jug/lyx/lyxdoc/ExternalMaterial/ Is this yours Jürgen? Why is this not integrated in our manuals? Not mine. Jürgen Vigna's. I realized that after I send the message, sorry. But even this document doesn't rea

Re: [Cvslog] r25224 - /lyx-devel/trunk/src/LyXAction.cpp

Pavel Sanda wrote: Abdelrazak Younes wrote: These lfuns update/apply the 'free' floating font object that is used to repeatedly apply the same font (textstyle) to multiple cursor location. aha, this naming follows the implementation. imho incomprehensible from the users-point of view

Re: [Cvslog] r25224 - /lyx-devel/trunk/src/LyXAction.cpp

Abdelrazak Younes wrote: > These lfuns update/apply the > 'free' floating font object that is used to repeatedly apply the same font > (textstyle) to multiple cursor location. aha, this naming follows the implementation. imho incomprehensible from the users-point of view. >> what about to rena

Re: [Cvslog] r25224 - /lyx-devel/trunk/src/LyXAction.cpp

Pavel Sanda wrote: [EMAIL PROTECTED] wrote: Author: sanda Date: Tue Jun 10 23:37:40 2008 New Revision: 25224 +/*! + * \var lyx::FuncCode lyx::LFUN_FONT_FREE_APPLY + * \li Action: Toggle user-defined text style. + * \li Syntax: font-free-apply + * \li Origin: leeming, 12 Mar 2003 + * \endvar +