haven't followed the thread, but i would be in favor of having one align
function and apply the alignment to the selection (just like we do now with
table lines): if you want to change the alignment of a column, select the
column and then set the alignment.
edwin
__
jean-marc wrote:
> Currently, listings reuses ERT (?) to handle spaces. We could of course
> decide to have a new parameter to alloz multiple normal space. Even
> better, we could use \obeyspaces in LyX-Code to make normal spaces
> work like ~. This would solve many problems IMO (but create interes
richard wrote:
> ~ is the only way to preserve multiple spaces in LaTeX.
i don't think so, it depends on the environment. listings for example preserves
multiple spaces.
what i am after is listings type behavior, but using Style instead of
InsetLayout and for that i don't want the ~ nor the ex
i am fiddling with a layout i'm trying to put together
i want to define an environment that contains plain text.
i have the following
Style Stata-Log
LatexType Environment
LatexName stlog
FreeSpacing true
KeepEmpty tru
richard wrote:
> The unicodesymbols file lists things like this: \"{o} and not like this: \"o
> So G\"odel doesn't get translated.
isn't it possible to have multiple entries in the unicodesymbols file?
> The only point I would put forward is to take care that saturation is not too
> low, for accessibility reasons.
if this turns out to be an issue we could always add the saturation level to
the preferences...
> I'm open for new ideas.
or lower the saturation for deletions as in attached
edwin
<>
Jürgen wrote:
> Rather than replacing our (also KDE-derived) icon set with another one, it
> would be worth investigating into the use of stock icons, i.e. using the icon
> theme currently used by the OS or DE.
i personally would really welcome an icon set based on a consistent palette and
design
> how are we going to say "no" to other scary tricks? ;)
i hope by getting rid of the need for many of them in the next release cycle...
to answer myself:
it turned out that \myheader is left undefined when no option is passed. so i
just define it (empty) and the following works
--beamerthememytheme.sty---
\def\myheader{}
\DeclareOptionBeamer{header}{\def\myheader{#1}}
\ProcessOptionsBeamer
\m
next time i would wait with going into beta after the summer and not just
before...
ed.
i am trying to achieve that when i do the following in the preamble of my
beamer presentation:
\usetheme[header=onlylogo]{mytheme}
the file headeronlylogo.pdf will be used as the background in my presentation,
and that when i declare
\usetheme{mytheme}
it will default to header.pdf
i have th
> Where do you think that LyX needs more attention?
polishing and the removal of ui hacks
> What feature do you think that LyX is missing badly?
being able to do a diff on two lyx docs and then use our change tracking user
interface to merge in the changes.
together with lyx' version control s
> You forgot that this is a file format change (increase file format and add the
> necessary lyx2lyx conversion/reversion routines).
and some ui: menu entries, dialog ...
i wonder whether the shouting is also part of her hypnotherapy:
http://www.wendi.com/
From: news [EMAIL PROTECTED] On Behalf Of Jürgen Spitzmüller [EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 16:38
To: lyx-devel@lists.lyx.org
Subject: Re: r27622 - /
Abdel wrote:
> qsdqDDSQSD
and we are supposed to believe there is no beer...?
Jürgen wrote:
> Andre Poenitz wrote:
> > Meeting starts now. Brace for impact.
>
> Have fun!
indeed. and don't OD on beer, expectations are high... ;-)
> Sold. I like it. :-)
glad to hear that, note that i invented a webpage:
http://wiki.lyx.org/LyX/ReleaseNotes160
jean-marc wrote:
> It is definitely annoying. However, I am ready to bet that the
> release of 1.6.0 will bring to
> our attention some bugs much worse than this one.
party pooper...
i changed the order a bit, and some minor edits
(just a suggestion of course)
Public release of LyX version 1.6.0
===
We are pleased to announce the release of LyX 1.6.0.
LyX is a document processor that encourages an approach to writing
based on the structure
perhaps simply:
You can download LyX 1.6.0 from http://www.lyx.org/Download
instead of
You can download LyX 1.6.0 here:
ftp://ftp.lyx.org/pub/lyx/stable/lyx-1.6.0.tar.gz
ftp://ftp.devel.lyx.org/pub/lyx/stable/lyx-1.6.0.tar.gz
Prebuilt binaries (for linux distributions, Mac OS
false alarm. dirty tree i think.
sorry for the noise...
edwin
...we loose tabular lines.
note that reading tabular lines used to work, so something must've broken it...
edwin
added suggestions and simplified the general donation
edwin
abdel wrote:
> I am fine with the changes and simplifications except that I miss the
> paragraph that indicates how to suggest a project. But perhaps you're
> right that this should be decided on the feature poll page.
i removed that because it seemed incomplete: it only mentioned how to find
ide
abdel wrote:
>> http://www.lyx.org/Donate-Draft
>
> I reorganized it a bit following Ed's advice.
i did some more edits. perhaps someone with an opinion can have a look?
thanks, ed.
will have a look at it tonight...
ed.
From: Abdelrazak Younes [EMAIL PROTECTED]
Sent: Tuesday, October 28, 2008 09:05
To: Christian Ridderström
Cc: lyx-devel@lists.lyx.org
Subject: Re: Donation page (Was: windows lyx installer)
On 28/10/2008 08:47, Christ
perhaps we should think about adding a checked checkbox "Tell me how to
donate!" linking to http://www.lyx.org/Donate at the end of the windows
installer.
another suggestion is to move the projects table to the top of the webpage and
add a first row with a "General Donation". there is too much
> > return, depth-decrement
> > (as in other word processing software)
>
> Hmmm
i'll bet you a beer that this is what the overwhelming majority of lyx users
are doing to end the current 2nd level itemize and continue the 1st level one...
> > return: new item at current level
> > m-return: standard in itemize at current level
> > reset: reset to standard, and also reset level
> >
>
> So there is no way to end the current 2nd level itemize and
> continue the 1st level one?
return, depth-decrement
(as in other word proce
> No, but I'm with you on that case. I think Standard in itemize is fairly
> normal.
i am also with both of you, what i am suggesting is:
if you are in itemize
return: new item at current level
m-return: standard in itemize at current level
reset: reset to standard, and also reset l
> I begin to wonder whether accusing the other side of sophism at each
> argument is not some kind of meta-sophism, or even maybe the Mother
> Of All Sophisms.
i did not accuse you of sophism at each argument, only when you referred to "it
make sense because it is possible in latex", "there might
> I think it is wrong to have LFUN_LAYOUT do something else than just
> change the layout.
trying the semantic arguments now? (another sophism ;-)
maybe the nesting level is not formally part of the layout *in lyx*, it is
definitely layout. so i do not see why LFUN_LAYOUT should not change it...
> So at least we should try to be predictable.
reset = 0 always
seems pretty predictable to me...
> Resetting to 0 is too rude.
because...
> So with you proposal, I cannot set a paragraph to standard in an
> enumeration easily anymore, right?
that would be my M-return
> Tsk, tsk, I will not
> I use that :-)
and you can still use it, but you would need to explicitly indent these
sections (which makes more sense here i think)
> I agree, however, that the expected case is non-nested for sections.
my point indeed
> For standard and quote and quotation, however, I'm not so sure.
in w
> I understand that putting a section in a nesting seems weird but (1)
> LaTeX allows it and (2) I would not be suprised to find a class that
> uses that in some way (people do weird things).
smells like a sophism to me...
> Then it is a matter of educating our users, and maybe also to
> make nes
> This is indeed annoying but
> 2/ the real problem is this endframe business that is a kludge to use
> beamer with LyX. The real solution would probably be to use an InsetFlex
> instead.
it is not only endframe, but if one switches from an itemize to a section,
subsection, part etc this is not i
j-m wrote:
> I do not think so :)
care to elaborate?
it is in:
http://www.lyx.org/trac/changeset/27007
edwin
From: José Matos [EMAIL PROTECTED]
On Tuesday 21 October 2008 07:40:38 Jürgen Spitzmüller wrote:
> rgheck wrote:
> > Seems perfectly sensible to me.
>
> +1
OK.
> Jürgen
--
José Abílio
> Arghh, I did not have time yet to look at it... even to the initial
> problem.
it is very simple; we should set the depth parameter to zero when resetting a
paragraph to say standard (or section etc).
the only case where we would like to preserve the nesting depth is if we switch
from an item
edwin wrote:
> the attached puts it in:
>
> void Paragraph::applyLayout(Layout const & new_layout)
ok to commit this version?
a colleague of mine did not realize that the error list was clickable, and that
clicking on an error would show the error message and send the cursor to the
offending part in the document. so for every error she would bisect her
document to trace it down (i know what you are thinking).
one of t
> What don't you use trunk version instead?
> A number of
> critical bugs have been fixed since rc3.
too lazy to compile the installer i guess. i will update and see what happens...
> There's a nasty one involving selection in tables...
but this one is not biting me.
the strange thing is that l
as the subject says, lyx rc3 is very unstable here at work for me and crashes
regularly with messages like:
L'instruction à "0x670c899d" emploie l'addresse mémoire "0x0004". La
mémoire ne peut pas être "read".
usually when i click reply in outlook, and once when I started word (gasp!)
I kn
> i have tried this patch and don't agree :) 1. vertical size
> of dialogs are again greater 2. while in some cases groupbox
> helps to distiguish groups in many
>other cases this distinction is quite clear and group box
>version looks odd.
and it isn't even Friday...
> my preffered solution for now is to change lists back to
> symmetrical state and change module names.
i can't disagree with that
just note that this fiddling with layout based on what happens to be your
locale and the modules names on october 20, 2008 is bound to be somewhat
arbitrary...
> the logic is simple - there is clear asymmetry wrt usage - in
> most cases the right panel won't be used for those theorems envi...
it's all in the eye of the beholder i s'pose
...
another possibility is to change at one point the interface to a single
listview with checkable items (that can
> because i have oposite view on "what ugliness is"? :)
that's one reason of course ;-)
the other is that i don't understand the logic for the asymmetry since left and
right can contain the same items...
the attached puts it in:
void Paragraph::applyLayout(Layout const & new_layout)
which is as deep as we can get here...
edwin
jean-marc:
> I did not try it, but I do not like the approach. We do not need more
> ad-hoc solutions in the code. It is not clear to me that enumeration
> should get th
jean-marc:
> I did not try it, but I do not like the approach. We do not need more
> ad-hoc solutions in the code. It is not clear to me that enumeration
> should get their own special treatement.
>
> I'll try to propose something more constructive tomorrow.
you might like the attached better (i d
jean-marc wrote:
>> the attached patch resets the nesting when resetting and item/enum to
>> something else
>>
>
> I did not try it, but I do not like the approach. We do not need more
> ad-hoc solutions in the code. It is not clear to me that enumeration
> should get their own special treatement.
>Comments are welcome,
how can anyone disagree...
fwiw, the patch here
http://leuven.economists.nl/lyx/groupboxes.zip
replaces all the flat groupbox with drawn ones...
edwin
> I would prefer it if we could agree on some design criteria first.
sure. one possibilty would be to have fully drawn group boxes at the first
level and try to have flat ones if they are nested to avoid clutter...
Abdel wrote:
>> Edwin write:
>> the attached patch resets the nesting when resetting and item/enum to
>> something else
>>
> I like it.
ok to commit?
feel free to change it...
edwin
Jürgen wrote:
> The thing I do not like with these "flat" Group boxes is that you
> don't see where the Group actually ends
where the next one starts. there should be no ambiguities...
> i did this consciously because the old layout with horizontal bar is ugly to
> see.
the current solution is even uglier, and you still get a horizontal scroll bar
with the selected items...
> although i don't persist on this assymetric view, i'm against simply
> restoring the old layout.
wh
small layout tweak to the document class panel
ok?
latexui.patch
Description: latexui.patch
the manual tweaking of the widths now is usually not a good idea. we also get
asymmetric widths now, so i'd like to suggest restore the old layout as in
attached
ok?
edwin
modules.patch
Description: modules.patch
the attached patch resets the nesting when resetting and item/enum to something
else
personally i like this behavior much better
opinions/objections?
edwin
From: leuven edwin [EMAIL PROTECTED]
Sent: Saturday, October 18, 2008 12:12
To: lyx-devel
Jürgen wrote:
> I've just done that.
thanks
as long as one sees the full name in a tooltip when the mouse is over the item
it wouldn't shock me.
something else: since this is now in its own panel i'd suggest to remove the
groupbox...
edwin
when i reset the last line in the attached document (which is a nested item) to
standard, the paragraph is still part of the itemizing environment.
someone at work who was not aware of this behavior did something similar and
reset a nested item to an endframe and ended up with a document that di
> I think we already had this discussion.
i must be getting old. but then again, some discussions are worth forgetting...
i would like to suggest to change lyx's default background color to white for
1.6
white seems to be the default background color for text entry on most
platforms...
laundry.patch
Description: laundry.patch
> i don't think so since:
> 1) slider can be still used
> 2) the point of this check box has nothing to do with slider
maybe i will understand it when i see it...
>> so in the second use case you basically want to ignore/disable the slider?
>
> _basically_ i want persistent tree view in the way i
> uncollapsed it even if some changes to the paragraphs of
> document happen.
this is a "yes" i suppose.
so wouldn't adding a toggle button which disables the sli
> when you want to hold the current toc behaviour. Typical
> example is normal writing or quick moving through the text -
> outliner gives you the info about the context around, when
> you move out of the current section it gets collapsed and new
> section structure is uncollapsed. this keeps the
> > > my proposal is to add checkbox just below sort and it
> would be good
> > > to have short naming. what about 'Keep' with 'Keep
> uncollapsed state'
> > > tooltip?
just a last clarifying question: when would one like to uncheck this checkbox?
>>> URL: http://www.lyx.org/trac/changeset/26668
>>
>> the same bug seems to be present in 1.5, so perhaps this is a candidate
>> for branch as well...
>
> Indeed. Could somebody prepare a patch? I don't have time ATM to do it myself.
patch attached. copy pasting from abdel's. cannot test it here
> Author: younes
> URL: http://www.lyx.org/trac/changeset/26668
the same bug seems to be present in 1.5, so perhaps this is a candidate for
branch as well...
Abdel wrote:
> I am not very keen on adding this check box
if i understand things correctly this checkbox is supposed to hide the symptom
without solving the underlying problem. am i right?
> but if this is the only solution to keep each type of user happy, why not...
because it leads to ui-blo
since you insist ;-) i would prefer this:
> + author1
>Deletion:
>Insertion:
> + author2
>Insertion:
>Deletion:
> ...
>
> Why not simply rename that to "Document Structure"?
that works in english, but not necessarily in all languages...
?
edwin
also: could you reverse the sort order in the combobox in the toc panel? the
toc is used most often so it would be nice to have it on top...
bind-sequence
?
> But if we used a different delimiter?
that would've been my next question...
is it possible to put a command sequence among the alternatives?
> So from my point of view rc3 can be released.
would be nice to fix this one too
http://bugzilla.lyx.org/show_bug.cgi?id=5225
i suspect the fix is real easy, but am away on conference so can't look into it
right now...
> We also need to fix the selection painting within Inset.
and *of* insets themselves.
f.e. if you change the color of selected text to white in preferences you will
see that say the numbers of sections stay black (whereas we would then like
them white). it would be nice if this type of stuff i
> - it is very sneaky to remove the View menu again.. Moving all items
> from the Window menu into the View menu would ALSO be an option...
not sneaky, i just moved the 2 items in the view menu. the window menu was much
fuller so i makes sense not to name it view. of course we could s/window/view
>> collapsed status is also saved in the document (like it or not), so
>> i have put this in the file menu for now
>
> I would not do that. File menu is more for physical state of the
> document (so I guess Compressed can belong there). If you do that, why
> not put "Insert Table Float" too???
hey
as in attached
menu order:
file, edit, format, insert, math, go to, typeset, window, document,
application, help
toolbars is in application
fullscreen in window
i like this myself (if I can say that..)
hig2.inc
Description: hig2.inc
hig2.ui
Description: hig2.ui
> > but let's see:
attached the reworked menu, following most of your suggestions
> But there is a View menu everywhere - in the XP HIG, Vista
> HIG, Apple HIG, Wordpad, Office 2003, ...
so now possibly also soon in lyx...
> Don't refuse just because you don't like it.
that's what all religiou
konrad wrote:
> Edwin (and others),
>
> great thanks for starting to work on this!
thanks for having a look as well...
> I have a number of suggestions for changes, strictly based on
> the HIG [1] (except those sentences starting with IMO).
just as a side note; i think it is good to have some di
pavel wrote:
> isn't possible somehow to get navigation panel and viewing
> source items together? its a different logic, but my brain
> somehow search for the floating dialogs on the same place and
> maybe i'm not alone.
in the attached they are both in the window menu
i moved the open/close all
>mutable bool margin_beg_sel;
>mutable bool margin_end_sel;
if these bools indicate whether you want to draw some selection to either the
left or right, why not simply call them:
leftmargin_sel
rightmargin_sel
(just ignore me if it shows that i didn't study your patch)
> This patch solves the problem indeed - I hope this makes it into 1.6svn soon!
ok, i've commited this
> There is another wide table navigation bug left.
the left arrow bug should also be gone with the commit
> This also need to happen on cursor up/down:
will have a look at this when i have so
> contrary I'll call 15.11. "final". Bad luck for Ed, but apart from that
> it does not look too bad.
bad luck indeed (with the exception of missing abdel's snoring... )
Helge Hafting wrote:
> Tables too wide for the main window scroll sideways when accessing cells
> beyond the edge.
>
> This breaks if the cell contain any kind of inset. LyX will then
> jump back to the left edge, leaving you with an invisible
> cursor until the cursor comes out of the inset.
the
Abdel Lgb José Chr Ed
04.10 130 4 0
11.10 532 4 0
18.10 330 4 3
25.10 503 4 0
01.11 434 5 3
08.11 335 5 0
15.11 335 4 0
22.11 335 4 3
29.11 335 4 0
06.12 330
> You could come for the weekend only ;-)
yes, but that will depend on the date of the meeting
> Really?
would i lie about such a thing?
> Paris?
beh oui
> Perhaps we could transfer the meeting there :-)
what we will loose in the quality of the beer, we will gain in the quality of
the food.
abdel wrote:
> Anybody else from neighboring countries?
i am interested in coming, but am a bit constrained since i started my new job
this week...
> Netherlands (Edwin?) I hope my geography is correct :-)
i am afraid not: i am playing on the french team these days ;-)
regards, ed.
joost wrote:
> Why is cmd.exe being used? Do you know where in the code this error occurs?
cmd.exe is being used when running configure.py. don't ask me why (or why not).
the first error occurs as in the thread before, at this call
log = open(logfile, 'w')
which is now line 910.
regards, e
hi guys,
before I had some troubles with running lyx from the network drive here. see
this thread for details:
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg112416.html
it had something to do with cmd.exe and UNC paths.
now it turns out that the following:
http://support.microsoft.co
96 matches
Mail list logo
