Vincent van Ravesteijn - TNW wrote:
> Would it make sense to reuse the already existing outline_up outline_down
> code, or to use the new code also in the existing code? Now, it looks like
> we duplicate the code to move paragraphs.
I think improvements are certainly welcome.
Jürgen
Andre Poenitz wrote:
> I do not completely disagree, but the environment is called "align", not
> "Align". I would consider this as some kind of opposite of a "proper
> noun" that's not subject to changes by capitalization.
As I stated several times, if we do this, we will have to adapt many many
Pavel Sanda wrote:
> > If it was done consistently. But it isn't.
>
> but the solution is not to smash the correct ones. considering
> that tex is case sensitive and case sensitivity comes in play
> eg \huge vs \Huge, making such capitalization in menu tends to
> confuse things.
Do you really thin
> Thanks for the script. It indeed does automate everything, but I think
> that it is wasteful always downloading and compiling Qt as well as the
> svn branch. It could be made to check what actually needs doing.
> When I'll find the time I'll try to polish and add it to the wiki page.
Enrico, it
>Author: sanda
>Date: Sun Jun 28 12:37:34 2009
>New Revision: 30281
>URL: http://www.lyx.org/trac/changeset/30281
>
>Log:
>Keep numbering
I would rather adjust the numbering and keep LFUN_OUTLINE_* together, the same
for LFUN_VC_*.
Vincent
>Author: spitz
>Date: Sun Jun 28 10:40:34 2009
>New Revision: 30278
>URL: http://www.lyx.org/trac/changeset/30278
>
>Log:
>Implement LFUN_OUTLINE_DRAGMOVE.
>
>Contribution by Rob Oakes.
Would it make sense to reuse the already existing outline_up outline_down code,
or to use the new code als
On Sat, Jun 27, 2009 at 04:32:00PM -0400, Ben M. wrote:
> Enrico's instructions on the Wiki about how to install LyX in Cygwin
> are extremely well-written:
> http://wiki.lyx.org/LyX/LyXOnCygwin
>
> Unfortunately, it takes me about half the day to follow them, since
> compiling takes so long, a
Jean-Marc Lasgouttes wrote:
>> to which debug level should it go?
>
> I think you can remove it.
ok
pavel
Le 29 juin 09 à 00:06, Pavel Sanda a écrit :
hi,
when i go through modules list i get
LaTeXFeatures.cpp(402): from=[literate] to=[latex]
LaTeXFeatures.cpp(402): from=[sweave] to=[latex]
to which debug level should it go?
I think you can remove it.
JMarc
hi,
when i go through modules list i get
LaTeXFeatures.cpp(402): from=[literate] to=[latex]
LaTeXFeatures.cpp(402): from=[sweave] to=[latex]
on console produced by
bool LaTeXFeatures::isAvailable(string const & name)
{
string::size_type const i = name.find("->");
if (i != string:
hi,
what about adding this into trunk?
pavel
#\DeclareLyXModule[comment.sty]{Print Comments}
#DescriptionBegin
#Typeset comment notes in LyX. When used with notes-mutate lfun,
#it can be used even for normal LyX notes.
#DescriptionEnd
Format 11
AddToPreamble
\usepackage{comment}
\
Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
> > having latex keywords in
> > menu verbatim-like is constinent just from another angle.
>
> If it was done consistently. But it isn't.
but the solution is not to smash the correct ones. considering
that tex is case sensitive and case sensitivity c
On Sat, Jun 27, 2009 at 07:13:32AM +0200, Jürgen Spitzmüller wrote:
> And not only that.
>
> After re-consulting a HIG (the Gnome HIG since KDE's is inaccessible ATM, but
> they should be identical in this regard), I came up with the following
> changes.
>
> Objections?
>
> Jürgen
> Index: li
Pavel Sanda wrote:
> having latex keywords in
> menu verbatim-like is constinent just from another angle.
If it was done consistently. But it isn't.
Jürgen
Pavel Sanda wrote:
> Jürgen Spitzmüller wrote:
> > I believe one cause of the problems we have with settings that get lost
> > after reconfigure is the following:
>
> nothing against this patch, but i think the root of the problems is
> elsewhere;
I believe the problem has multiple causes. This is
Jürgen Spitzmüller wrote:
> You "feel", but the Inteface Design Standards state otherwise. I do not say
> that your feeling counts less than the Standards, but I think it would make
> more sense to do what most apps do.
hig shouldn't be applied blindly as a rule and having latex keywords in menu
Jürgen Spitzmüller wrote:
> I believe one cause of the problems we have with settings that get lost after
> reconfigure is the following:
nothing against this patch, but i think the root of the problems is elsewhere;
i need to reestablish my settings every other day in trunk which version
doesn'
Le 28 juin 09 à 15:37, Jürgen Spitzmüller a écrit :
I think it would make more sense to use the PACKAGE variable, i.e.
lyx[-version-suffix], as a config file name. Then session parameters
would
persist over minor and even major version changes, and one still
would have
separated configuration
I believe one cause of the problems we have with settings that get lost after
reconfigure is the following:
The settings are saved by Qt in a config file that is named from the LyX
version. Thus we get a new, empty config file after every version change, and
thus the toolbar changes etc. are l
Jürgen Spitzmüller wrote:
> Anyway, we can as well decide to follow the Windows User Experience
> Interaction Guidelines. As long as we follow any Standard.
BTW even though the Windows User Experience Interaction Guidelines recommend
sentence-style for Menus, they also point out that one should r
Rob Oakes wrote:
> Dear LyX Developers,
>
> The LyX project has permission to utilize my contributions and release them
> under the GNU Public License, version 2.0 or later.
>
> Rob Oakes
Thanks. I did some final polishment and committed the stuff.
Jürgen
Pavel Sanda wrote:
> well, i feel that the layout combo is a different thing, but i'm not going
> to flame for this.
You "feel", but the Inteface Design Standards state otherwise. I do not say
that your feeling counts less than the Standards, but I think it would make
more sense to do what most
Enrico Forestieri wrote:
> > I don't think we should setup our own rules, but do what most other
> > applications do. Since the rules are surprisingly coherent in the HIGs I
> > consulted, so I do not see a reason why we should diverge from that.
>
> Fine. However, I would take them as guidelines r
23 matches
Mail list logo
