Neal Becker wrote:
> AFAICT it's not possible to insert \begin{frame}[fragile]...\end{frame}
> either - the only way I could get it to work is to include a file that
> contains that.
I managed to do that. I think it is important that you have an EndFrame before
it.
Jürgen
Jürgen Spitzmüller wrote:
> Neal Becker wrote:
>> I can find no way to do this within lyx. I hope for a solution.
>
> It's not possible (apart from using \begin{frame}[fragile]...\end{frame}
> in ERT):
> http://bugzilla.lyx.org/show_bug.cgi?id=3710
>
> Jürgen
AFAICT it's not possible to insert
Neal Becker wrote:
> I can find no way to do this within lyx. I hope for a solution.
It's not possible (apart from using \begin{frame}[fragile]...\end{frame} in
ERT):
http://bugzilla.lyx.org/show_bug.cgi?id=3710
Jürgen
Jean-Marc Lasgouttes wrote:
> Vincent van Ravesteijn writes:
> > - Labels of Insets with a background color defined get this color as
> > their label (like Note is now, this can be easily recognized),
> > - Labels of Insets with no background color get the default value.
>
> In the case of Notes,
Vincent van Ravesteijn writes:
> - Labels of Insets with a background color defined get this color as
> their label (like Note is now, this can be easily recognized),
> - Labels of Insets with no background color get the default value.
In the case of Notes, I find the yellow-on-grey quite unreada
Vincent van Ravesteijn wrote:
> I was a little bit too quick... it seems it is quite random what we do..
> Floats get the "collapsable inset text", Boxes/Listings get black which is
> not changeable, Note and Greyedout have custom values...
> but we should make an end to this.
>
> What shou
Vincent van Ravesteijn schreef:
Ah soo...
I was a little bit too quick... it seems it is quite random what we
do.. Floats get the "collapsable inset text", Boxes/Listings get black
which is not changeable, Note and Greyedout have custom values...
but we should make an end to this.
What
Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
Pavel Sanda schreef:
hi,
its impossible to see labels on collapsed inset listings on non default
color scheme. one solution is to add new color for listings foreground
second one is to give standard collapsable-inset color for text lab
Vincent van Ravesteijn wrote:
> Pavel Sanda schreef:
>> hi,
>>
>> its impossible to see labels on collapsed inset listings on non default
>> color scheme. one solution is to add new color for listings foreground
>> second one is to give standard collapsable-inset color for text label
>> as other in
Pavel Sanda schreef:
hi,
its impossible to see labels on collapsed inset listings on non default
color scheme. one solution is to add new color for listings foreground
second one is to give standard collapsable-inset color for text label
as other insets do. what would you prefer?
pavel
The s
> Is this correct? Has 1.6svn been responsible for loss of data? Or would
> it be safe enough to use on something important?
I would not use any svn version for serious work, unless you really
need some feature.
As of this parameter-editor dialog, I think Edwin can simply transform
the all_params
On Mon, 2007-10-01 at 14:47 +0100, John Levon wrote:
> I just came across this. Is there a bug filed on fixing this UI?
> I'm a bit concerned that new UI isn't getting the review it deserves.
I for one am afraid to try it because I am working only on one very
important document, and I hear too man
> Edwin is working (AFAIR) on a property editor style interface.
brooding is a better word than working
...
if someone finds time: it would be useful to store package information in a
definition file and parse this, where we would like the following.
parameter
description
type {e.g. LENGTH,TE
On Mon, Oct 01, 2007 at 10:03:16AM -0500, Bo Peng wrote:
> > Why isn't this a listbox + tooltips?
>
> Because there are 163+ options (and most of them are rarely used).
There are ways to deal with this.
> Edwin is working (AFAIR) on a property editor style interface.
Cool.
john
> Why isn't this a listbox + tooltips?
Because there are 163+ options (and most of them are rarely used).
Edwin is working (AFAIR) on a property editor style interface.
Bo
John Levon wrote:
> It's just plain bizarre. (A good rule is: if
> you're inventing a new form of UI, you're most likely doing something
> wrong.)
You see, we really missed you ;-)
Jürgen
John Levon <[EMAIL PROTECTED]> writes:
> (A good rule is: if you're inventing a new form of UI, you're most
> likely doing something wrong.)
Very true.
JMarc
On Mon, Oct 01, 2007 at 04:09:24PM +0200, Jürgen Spitzmüller wrote:
> > I just came across this. Is there a bug filed on fixing this UI?
> > I'm a bit concerned that new UI isn't getting the review it deserves.
>
> No.
>
> What's the problem?
We have a list of options that's presented as some h
John Levon wrote:
> I just came across this. Is there a bug filed on fixing this UI?
> I'm a bit concerned that new UI isn't getting the review it deserves.
No.
What's the problem?
Jürgen
Dov Feldstern wrote:
> I'm attaching a series of patches which are a step in the right
> direction, but still not there yet. However, I think that they only make
> things better, so I would be happy to have them applied once someone
> looks them over...
I let others comment on it. These patches mi
Dov Feldstern wrote:
Juergen Spitzmueller wrote:
Jean-Marc Lasgouttes wrote:
Juergen, could you tell me when setting local_font is necessary? I did
not see the problem when creating a new listing inset with caption.
The problem showed up when you created a listings inset with a caption
befor
Dov Feldstern wrote:
> My previous patch handled the encoding --- I still think it should be
> applied in full (I will send in an updated patch soon). Jurgen had said
> he applied only those parts he understood, so I gather that the rest was
> not understood well enough --- I will try to comment it
Jürgen Spitzmüller schrieb:
Uwe Stöhr wrote:
But this is then a bug. LyX currently swallows all author informations
without confirmation. This is in my opinion a dataloss!
I don't think so. The author information was introduced and currently is
actually only there for change tracking
Uwe Stöhr wrote:
> But this is then a bug. LyX currently swallows all author informations
> without confirmation. This is in my opinion a dataloss!
I don't think so. The author information was introduced and currently is
actually only there for change tracking purposes. Because of bug 3764, this
>> In principle yes. But please don't delete all authors.
>
> I didn't do this explicitly. This is the consequence of rev 19019.
But this is then a bug. LyX currently swallows all author informations without confirmation. This is
in my opinion a dataloss!
Furthermore it is a bug that I can set m
Uwe Stöhr wrote:
> In principle yes. But please don't delete all authors.
I didn't do this explicitly. This is the consequence of rev 19019.
> The note should be
> in a greyed-out note as the other ones in the document. I can also do this
> later today and commit.
Yes, please do that.
Jürgen
Jürgen Spitzmüller schrieb:
Uwe, OK to xommit the attached?
In principle yes. But please don't delete all authors. The note should be in a greyed-out note as
the other ones in the document. I can also do this later today and commit.
regards Uwe
Pavel Sanda wrote:
> you are right. feel free to change it the way you like and commit it.
Uwe, OK to xommit the attached?
Jürgen
Index: lib/doc/EmbeddedObjects.lyx
===
--- lib/doc/EmbeddedObjects.lyx (Revision 19077)
+++ lib/doc/Emb
>So how about something like
you are right. feel free to change it the way you like and commit it.
thanks
pavel
--- EmbeddedObjects.lyx 2007-07-03 12:55:59.0 +0200
+++ /trash/embed.lyx2007-07-15 18:04:12.0 +0200
@@ -28202,6 +28203,10 @@
\end_inset
is recognized and printe
Pavel Sanda wrote:
> listings manual advices LuxiMono fonts from CTAN. i've tried them and it
> works well. i think this will be asked more often - what about little
> update of our docs ?
Good idea. However,
> + If you don't have bold keywords when typewriter family of fonts is used,
> + you can
>>> 3. Rather TeX question - when typewriter font family is set, keywords are
>>> no more bold (maybe it is not possible to typeset this font in bold,
>>> dunno)
>>
>> This is quite likely.
>
> You have to use a typewriter font that actually provides bold faces.
listings manual advices LuxiMono fo
Bo Peng wrote:
> > 3. Rather TeX question - when typewriter font family is set, keywords are
> > no more bold (maybe it is not possible to typeset this font in bold,
> > dunno)
>
> This is quite likely.
You have to use a typewriter font that actually provides bold faces.
Jürgen
Pavel Sanda wrote:
> > Known problems... nobody has paid enough attention on them though.
>
> should i file new bug ?
No, this is bug 3582, I think.
Jürgen
> Known problems... nobody has paid enough attention on them though.
should i file new bug ?
> fillcolor=\color{red}
aha! '=' was the missing letter :))
> This is also a known bug (have to check bugzilla for bug number) that
> is, however, nontrivial to fix. My suggestion would be writing code
First thing - the box around inset has not length of the whole line.
Second - try to write some text and delete it - the box is not correctly
repainted
and the deleted letters remain displayed.
Known problems... nobody has paid enough attention on them though.
2. I would like to diff
Yes, I do mean the latter. It's just like a printer dialog: choose print to
device or print to file. If this is hard to implement, then in the interim
can we just put some text on this dialog that points the user to the insert
child doc?
File listings needs a filename + all the options
Normal
Bo Peng wrote:
>> Make external file an option under listings insert would be more
>> intuitive.
>
> Do you mean menu items
>
> insert ->
>program listing
>program file listing
>
> or something in the listings -> right click dialog? The latter is
> difficult because file listings is not
Make external file an option under listings insert would be more intuitive.
Do you mean menu items
insert ->
program listing
program file listing
or something in the listings -> right click dialog? The latter is
difficult because file listings is not an option of a normal listing
(which co
On Wednesday 11 July 2007, Bo Peng wrote:
> > I can't figure out how to use external file with lyx. I only see 1 kind
> > of insert for 'program listing', and nothing in the listing options that
> > looks like a file name.
>
> Insert -> File -> Child Document -> Include Type -> Listing. You will
>
On Wednesday 11 July 2007 17:03:50 Bo Peng wrote:
>
> Insert -> File -> Child Document -> Include Type -> Listing. You will
> have to manually enter options like firstline in the option box.
>
> I am not sure what we can do to make this easier to access... any idea?
Merge graphics, external, inc
I can't figure out how to use external file with lyx. I only see 1 kind of
insert for 'program listing', and nothing in the listing options that looks
like a file name.
Insert -> File -> Child Document -> Include Type -> Listing. You will
have to manually enter options like firstline in the opt
On Wednesday 11 July 2007, you wrote:
> > I am just trying out listings and it seems pretty good. One problem I
> > see is I just needed to re-indent a bunch of code (happens to be python,
> > so indent matters). I thought maybe I'd just edit the lyx file in emacs,
> > but found out that the form
I am just trying out listings and it seems pretty good. One problem I see
is I just needed to re-indent a bunch of code (happens to be python, so
indent matters). I thought maybe I'd just edit the lyx file in emacs, but
found out that the form of the listing in the lyx file was not very
friendly
On 5/15/07, Jürgen Spitzmüller <[EMAIL PROTECTED]> wrote:
InsetListingsParams.h: In
constructor 'lyx::InsetListingsParams::InsetListingsParams()':
InsetListingsParams.h:84: warning: 'lyx::InsetListingsParams::status_' will be
initialized after
InsetListingsParams.h:78: warning: 'std::string
lyx
On Thursday 10 May 2007 19:33:24 Bo Peng wrote:
> The problem is that I do not see your 'set language => shift left' report.
OK, now I see what happended, for some reason I have pressed the in line
button while selecting the language and I did not notice. My fault. :-)
> Bo
--
José Abílio
Create a new document and insert a listings inset, where is the inset? :-)
Centered. This might be wrong, but is intentional.
The problem is that I do not see your 'set language => shift left' report.
Bo
On Thursday 10 May 2007 16:01:48 Bo Peng wrote:
> > Not only the inset starts centered but when you change one of the
> > parameters (say the language) it goes to the left without any content
> > inside.
>
> I can not reproduce this either. Are you sure your listings inset is
> in a standard layo
> Why is the listings inset centered in the LyX view?
In theory, normal listing should occupy its own line and stay to the
left. inline listing should behave like an ERT or label box. I used
'display(){ return if not inline listing }' function to use displayed
layout so the listing inset is disp
On Thursday 10 May 2007 08:36:11 Herbert Voss wrote:
> Why is the listings inset centered in the LyX view?
> And rebuilding is done only when I move the mouse over the
> listing inset.
>
> latest svn
Not only the inset starts centered but when you change one of the parameters
(say the language)
On Wed, 3 Dec 2003, Jean-Marc Lasgouttes wrote:
> Indeed. I do not want changes in 1.3.x that will change the file
> format.
Excellent point, I'll start porting it to 1.4x now.
/Christian
--
Christian Ridderström http://www.md.kth.se/~chr
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Christian Ridderström wrote:
>> So... do you think it will/should be back-ported to 1.3.x?
Juergen> I don't think so. 1.3.x is a stable release. Only bugfixes,
Juergen> no new features.
Indeed. I do not want changes in
Christian Ridderström wrote:
> Actually, the problem can't be that difficult since I had Herbert's patch
> working in Xforms, and it is only since I started over by first adding
> a patch I got form Juergen (for Qt) that nothing is inserted.
Does that problem (nothing inserted) only occur in the q
52 matches
Mail list logo
