On Wed, Dec 10, 2003 at 10:21:11PM +0100, Georg Baum spake thusly:
>
> Martin,
>
> why does InsetBox writes a \noindent before \begin{minipage} in some cases?
> The old minipage inset did not do this. Does this imply that the conversion
> of minipage -> frameless box is not 1:1?
> Under what ci
When I install the RPM, I get this:
checking [for cmex10]... yes (pfb)
checking [for cmmi10]... yes (pfb)
checking [for cmr10]... yes (pfb)
checking [for cmsy10]... yes (pfb)
checking [for eufm10]... yes (pfb)
checking [for msam10]... yes (pfb)
checking [for msbm10]... yes (pfb)
checking [for wasy
> > I should have gotten a better error message than the above
> > traceback.
>
> This bug should be fixed in current cvs. The offending line should now
> be:
> opt.err.write(str(fmt) + ": " + error.format_not_supported)
>
> Please update and try again.
Thanks! Works as expected now.
See attached. I'd appreciate it if the LaTeX-savvy would cast an eye
over this:
int InsetExternal::latex(Buffer const & buf, ostream & os,
OutputParams const & runparams) const
{
+ if (params_.draft) {
+ os << "\\fbox{\\ttfamily{}"
+
Kuba Ober wrote:
> Methinks s/mislead/misled/, but you've had your mandatory punishment
> anyway and this is just a freebie :)
Well, if you think in American English, then there's nothing I can do
to help you.
> Now I'll better shut up lest the gods ban me for being OT and such
My turn to smile
Kayvan A. Sylvan wrote:
> On Wed, Dec 10, 2003 at 03:08:20PM -0800, Kayvan A. Sylvan wrote:
>> lyx2lyx is not working for an old document of mine and it does
>> not seem like a format error. I know lyx2lyx just got changed, so I
>> am reporting this:
>>
>> $ /usr/local/share/lyx/lyx2lyx/lyx2lyx m
> > Now that the insets are handling [was: there] THEIR own
> > FuncRequests, THERE is no need ...
>
> Ahhh. Context. I was mislead:
Methinks s/mislead/misled/, but you've had your mandatory punishment anyway
and this is just a freebie :)
> > Naughty boy, Angus, naughty boy :)
> > s/there/their/
On Wed, Dec 10, 2003 at 03:08:20PM -0800, Kayvan A. Sylvan wrote:
> lyx2lyx is not working for an old document of mine and it does
> not seem like a format error. I know lyx2lyx just got changed, so I
> am reporting this:
>
> $ /usr/local/share/lyx/lyx2lyx/lyx2lyx markpassion.lyx
> Traceback (most
lyx2lyx is not working for an old document of mine and it does
not seem like a format error. I know lyx2lyx just got changed, so I
am reporting this:
$ /usr/local/share/lyx/lyx2lyx/lyx2lyx markpassion.lyx
Traceback (most recent call last):
File "/usr/local/share/lyx/lyx2lyx/lyx2lyx", line 197, i
... attached is the patch I was trying to make at the start of all
this. With this all inset dialogs can be opened from the command
line:
dialog-show-new-inset bibitem
dialog-show-new-inset bibtex
dialog-show-new-inset box Boxed
dialog-show-new-inset box Doublebox
dialog-show-new-inset box Frame
Georg Baum wrote:
> Why do you remove these files?
Ok, you convinced me. See attached patch (also committed).
> I get this one if I try to read a 225 file with lyx with your box
> patch:
Should no longer be the case.
Roll on tomorrow and the discussion with José.
--
AngusIndex: development/C
Martin,
why does InsetBox writes a \noindent before \begin{minipage} in some cases?
The old minipage inset did not do this. Does this imply that the conversion
of minipage -> frameless box is not 1:1?
Under what circumstances should tex2lyx recognize that a \noindet belongs to
a minipage and ig
Kuba Ober wrote:
> Ekhm, this is not an argument. The two sentences you wrote above are
> both correct it seems, yet the one that I pointed to is still wrong
> :)
>
> Now that the insets are handling [was: there] THEIR own
> FuncRequests, THERE is no need ...
Ahhh. Context. I was mislead:
Kuba O
Am Mittwoch, 10. Dezember 2003 19:34 schrieb Angus Leeming:
> The attached patch changes the lyx format to 227
>
> \begin_inset Boxed -> \begin_inset Box Boxed
> \begin_inset Doublebox -> \begin_inset Box Doublebox
> \begin_inset Frameless -> \begin_inset Box Frameless
> \begin_inset ovalbox -> \be
> >> And so, I suspect, is André's assertion that the concept is no
> >> longer needed. Now that insets are handling there
> >
> > Naughty boy, Angus, naughty boy :)
> > s/there/their/
>
> Actually, you're exactly wrong.
I don't think so :)
> 'Where is this concept handled? Over there, in the ins
On Wed, Dec 10, 2003 at 06:34:07PM +, Angus Leeming spake thusly:
> The attached patch changes the lyx format to 227
>
> \begin_inset Boxed -> \begin_inset Box Boxed
> \begin_inset Doublebox -> \begin_inset Box Doublebox
> \begin_inset Frameless -> \begin_inset Box Frameless
> \begin_inset o
On Wed, Dec 10, 2003 at 05:43:49PM +, Angus Leeming spake thusly:
>
> Angus Leeming wrote:
> > having gone to the bother of defining InsetBox::BoxType, why do you
> > not use it to store InsetBoxParams::type, rather than use a string?
> > It seems perverse to me.
>
> Ok if I make the change a
On Wednesday 10 December 2003 18:34, Angus Leeming wrote:
[ No time now to comment all the other points, I will do it tomorrow]
> Also, I note that if I move lyxconvert_225.py to lyxconvert_226.py and
> then try and convert a 227 format file, I get an error that looks
> like a bug to me:
>
> $ ~/
Kuba Ober wrote:
> On Wednesday 10 December 2003 05:25 am, Angus Leeming wrote:
>> John Levon wrote:
>> > On Wed, Dec 10, 2003 at 09:34:25AM +0100, Andre Poenitz wrote:
>> >> As bold guess: 'noneditable' does not react at all, 'editable'
>> >> has some dialog attached and 'highly editable' is math
Angus Leeming wrote:
> The attached patch changes the lyx format to 227
Perhaps you'd like it?
--
Angus
box.diff.gz
Description: GNU Zip compressed data
On Wednesday 10 December 2003 05:25 am, Angus Leeming wrote:
> John Levon wrote:
> > On Wed, Dec 10, 2003 at 09:34:25AM +0100, Andre Poenitz wrote:
> >> As bold guess: 'noneditable' does not react at all, 'editable' has
> >> some dialog attached and 'highly editable' is math & inner text.
> >
> > T
The attached patch changes the lyx format to 227
\begin_inset Boxed -> \begin_inset Box Boxed
\begin_inset Doublebox -> \begin_inset Box Doublebox
\begin_inset Frameless -> \begin_inset Box Frameless
\begin_inset ovalbox -> \begin_inset Box ovalbox
\begin_inset Ovalbox -> \begin_inset Box Ovalbox
Angus Leeming wrote:
> having gone to the bother of defining InsetBox::BoxType, why do you
> not use it to store InsetBoxParams::type, rather than use a string?
> It seems perverse to me.
Ok if I make the change and also change this
\begin_inset Frameless
to this
\begin_inset Box F
Martin,
having gone to the bother of defining InsetBox::BoxType, why do you
not use it to store InsetBoxParams::type, rather than use a string?
It seems perverse to me.
--
Angus
The attached patch changes the lyx format to 226:
\begin_inset Note -> \begin_inset Note Note
\begin_inset Comment -> \begin_inset Note Comment
\begin_inset Greyedout -> \begin_inset Note Greyedout
The patch contains the associated changes to lyx2lyx.
It uses 'enum Type {Note, Comment, Greyout};
Jose' Matos wrote:
> How about
>
> def convert_note(lines):
> i = 0
> while 1:
> i = find_tokens(lines, ["\\begin_inset Note",
> "\\begin_inset Comment",
> "\\begin_inset Greyedout"], i)
> if i == -1:
> break
>
> lines[i] = lines[i][8:] + 'Note ' + lines[i][:8]
>
> Not tested
> "Felix" == Felix Kurth <[EMAIL PROTECTED]> writes:
Felix> Hello sorry for taking that long time. I was very busy. Here is
Felix> the patch. (against lyx-cvs)
Thanks a lot. This is now in both the main branch and the 1.3.x branch.
JMarc
On Wednesday 10 December 2003 15:40, Angus Leeming wrote:
>
> \begin_inset Note -> \begin_inset Note Note
> \begin_inset Comment -> \begin_inset Note Comment
> \begin_inset Greyedout -> \begin_inset Note Greyedout
>
> I'll up the file format to 226 and have been thinking about
> lyxconvert_225.py
>
Andre Poenitz wrote:
> Have you considered changing that params2string interface to
> void InsetBranchMailer::params2string(InsetBranchParams const &,
> ostream & data)
> {
> data << name << ' ';
> data << name_ << ' ';
> params.write(data);
>
Jose' Matos wrote:
> On Wednesday 10 December 2003 14:49, Angus Leeming wrote:
>> No need to pass the 'name' to each instance of InsetNoteMailer,
>> InsetBranchMailer as this name is fixed for each Mailer type.
>>
>> Committing now.
>
> Is the fileformat changed?
No, but my next one does chang
On Wed, Dec 10, 2003 at 02:49:15PM +, Angus Leeming wrote:
> No need to pass the 'name' to each instance of InsetNoteMailer,
> InsetBranchMailer as this name is fixed for each Mailer type.
>
> Committing now.
Concerning
-string const InsetBranchMailer::params2string(string const & n
On Wednesday 10 December 2003 14:49, Angus Leeming wrote:
> No need to pass the 'name' to each instance of InsetNoteMailer,
> InsetBranchMailer as this name is fixed for each Mailer type.
>
> Committing now.
Is the fileformat changed?
--
José Abílio
LyX and docbook, a perfect match. :-)
No need to pass the 'name' to each instance of InsetNoteMailer,
InsetBranchMailer as this name is fixed for each Mailer type.
Committing now.
--
AngusIndex: src/frontends/controllers/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/l
Andre Poenitz wrote:
> Cool stuff.
>
> I would have liked to do so for quite some while but did not find the
> courage lest I break the last working bit in LyXText...
;-)
The amazing thing is that it seems to fix a current bug in selection:
sometimes when selecting with C-Home, C-S-End the sele
Jean-Marc Lasgouttes wrote:
> I think that people using several versions of LyX should take care
> of using proper userdirs. You can do "./configure ...
> -with-version-suffix" to get 1.4.0cvs to use ~/.lyx-1.4.0cvs/ as
> userdir by default.
The strange thing is... I do. However, I also had a .lyx
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> What I noticed was, that when LyX 1.4CVS is started up without
Martin> the -userdir flag, it finds the configuration in ~/.lyx (put
Martin> there by my production LyX -- still 1.1.5fix1-1 as an RPM :-)
Martin> ), notices that it
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> My mental picture of the way forward is to disable the choice
Angus> of template until the user attempts to select a file (either
Angus> types it in or uses "Browse...").
Yes.
Angus> Thereafter, we'd activate the chooser but use
On Wed, Dec 10, 2003 at 12:37:41PM +, Angus Leeming spake thusly:
>
> Shouldn't this snippet of LyX's output be changed:
>
> -\begin_inset Greyedout
> +\begin_inset Note Greyedout
> collapsed false
>
> \begin_layout Standard
>
> some important comment
> \end_layout
>
> \end_inset
>
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Adding
...
Angus> Fixes things for me. I guess that all the 'insets-with-dialogs'
Angus> need to be added to this block.
Seems reasonable.
>> I guess it should default to the first one, or something.
Angus> See my ques
Shouldn't this snippet of LyX's output be changed:
-\begin_inset Greyedout
+\begin_inset Note Greyedout
collapsed false
\begin_layout Standard
some important comment
\end_layout
\end_inset
With the corresponding change in factory.C's readInset
- } else if (tmptok == "Note"
On Wed, Dec 10, 2003 at 10:25:41AM +, Angus Leeming wrote:
> John Levon wrote:
>
> > On Wed, Dec 10, 2003 at 09:34:25AM +0100, Andre Poenitz wrote:
> >
> >> As bold guess: 'noneditable' does not react at all, 'editable' has
> >> some dialog attached and 'highly editable' is math & inner text.
John Levon wrote:
> On Wed, Dec 10, 2003 at 09:34:25AM +0100, Andre Poenitz wrote:
>
>> As bold guess: 'noneditable' does not react at all, 'editable' has
>> some dialog attached and 'highly editable' is math & inner text.
>
> That's exactly correct.
And so, I suspect, is André's assertion that
On Wed, Dec 10, 2003 at 11:16:16AM +0100, Michael Schmitt wrote:
> Hi Andre,
>
> I have seen that you removed method "insertInset". Could you please tell
> me where the magic code is nowadays that prevents the insertion of an
> inset into an ERT inset? I can't find it.
This should be handled by
On Wed, Dec 10, 2003 at 09:34:25AM +0100, Andre Poenitz wrote:
> As bold guess: 'noneditable' does not react at all, 'editable' has some
> dialog attached and 'highly editable' is math & inner text.
That's exactly correct.
john
--
Khendon's Law:
If the same point is made twice by the same pers
Hi Andre,
I have seen that you removed method "insertInset". Could you please tell
me where the magic code is nowadays that prevents the insertion of an
inset into an ERT inset? I can't find it.
Thanks, Michael
On Fri, Dec 05, 2003 at 12:55:32PM +0100, Kornel Benko wrote:
> I know, but we were told to:
>
>
> So I tried.
This really doesn't apply to 140cvs right now :)
Complain about 1.3 though !
john
On Fri, Dec 05, 2003 at 10:29:03AM +0200, Martin Vermeer wrote:
> Interesting. It feels like direct manipulation to me.
>
> I am using it all the time in math. Discovered it by accident but
> grasped it straightaway, and now it is second nature. Delete the whole
> by trying to delete a part, or '
Andre Poenitz wrote:
>> Note that this attempt at brute force also fails:
>> LengthValidator::LengthValidator(QWidget * parent, const char *
>> name)
>> : QValidator(static_cast(parent), name),
>> no_bottom_(true)
>> {}
>> ../../../../src/frontends/qt2/lengthvalidator.C: In constr
Inset::insertInset and the toc's metrics/draw is unneeded.
This furthermore creates just one cursor slice for clicks on tabulars.
Official plan in one cursor slice for tabular. Better solution in the
long run (in the light of IU) and according to a few experiements not
much harder to implement.
On Wed, Dec 10, 2003 at 02:54:45AM -0300, Alfredo Braunstein wrote:
> this patch reworks selection handling a bit:
>
> - eliminates TextCursor::selection::start/end, in favour of
> TextCursor::selStart()/selEnd(), that compute the start and end of the
> selection on the fly from cursor and selecti
> > ../../../../src/frontends/qt2/lengthvalidator.C: In constructor
> >`LengthValidator::LengthValidator(QWidget*, const char*)':
> > ../../../../src/frontends/qt2/lengthvalidator.C:28: no matching
> > function for
> >call to `QValidator::QValidator(QWidget*&, const char*&)'
> > /usr/lib/qt
On Sunday 07 December 2003 13:20, Lars Gullik Bjønnes wrote:
>
> '-e' for log?
>
> '-l' or '--logfile' would be a bit better.
>
> imho... stderr should be for error in the program and perhaps debug
> messages.
But that is precisely what we are logging. And we offer the possibility of
redirectio
On Wed, Dec 10, 2003 at 12:28:26AM +0100, Michael Schmitt wrote:
> Just a short question (and hopefully also a short answer):
>
> What is the difference between a noneditable, and editable,
> and a highly editable inset?
If I knew...
As bold guess: 'noneditable' does not react at all, 'edita
53 matches
Mail list logo
