gilab migration (was: Re: Thanks!)

[Jean-Marc Lasgouttes]

Le 14/10/2022 à 14:42, Joel Kulesza a écrit :
Yes, I'm still hoping for replies to my March 8 email 
(https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg217242.html 
) 
and more narrowly my developer-list July 14 email.  Notably, I didn't 
receive any user accounts other than JMarc's to add to the private 
project to get additional feedback (or I missed them and cannot find 
them, and I apologize if that's the case).  Nevertheless, since March 8 
and within the developer-list thread following some additional 
discussion, I made the example issue migration public (here: 
https://gitlab.com/jkulesza/test_export_import/-/issues 
) but have 
received no feedback subsequently.  So, I am "stuck" between my March 
8th steps 2 and 3.


What I would propose at this point unless someone gives the feedback 
that what's shown is unworkable, no good, etc., is to cleanup my 
migration script, see if I can incorporate attachments and ensure issue 
number correspondence, and prove out the process again.  If/when proven, 
we'll be at the point of deciding whether to actually perform the 
migration, or not.  Because of current work conditions, I'm unsure about 
the timing of this, but unless I hear objections I'll pursue this plan.


Hi Joel,

I finally took some time to look again at the migration status, and here 
is my shopping list. Please tell us what is easy, doable, difficult, 
undoable, you name it.


I'll start from the top of the page of
https://gitlab.com/jkulesza/test_export_import/-/issues/1529
It might have been better to see more recent bugs, that do not date from 
bugzilla times and link to git commits.


I encourage my fellow developers to ask for access and chime in :)


Let's go for the list of things I'd like to see :

* issue number: it should be the same as in trac. It is weird actually 
that the gitlab issue number is larger than the trac one, I would have 
expected the opposite, due to deleted trac tickets


* issue date : should be the same as trac

* issue reporter : ditto

* the status of the tickets should be kept (transformed to labels if I 
understand well).


* the bug description: basically everything that is there should go to 
the proper place (see below)


* let's have a look at the table in the header. I can separate the 
entries in several categories


  - those who can go elsewhere: submitted (ticket date), reporter 
(created by), owner by (assignee), milestone (milestone), CC (notifications)


  - those that can maybe become labels : component, version (unless 
there is something I miss in gitlab for that)


  - those that can go away : last modified

  - those that I do not know how to handle (does gitlab handle that?) : 
priority, severity (maybe labels?)


* attachments: is there some ntive gitlab thing for that? If yes, 
attachments should be imported.


* Description : should be kept there

* Change history : comments should be individual gitlab comments, 
ideally with proper author name and date.


* the history of ticket (changes to properties) should be transferred 
(gitlab entries like "lasgouttes added label "regression" 1 month ago). 
That means that ideally the whole history of tickets should still be 
available.



This is of course very long and very demanding. This explains why I did 
not ask earlier, it felt like whining that your work was not good enough ;)


Thanks for the effort,
JMarc

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Thanks!

[Scott Kostyshak]

On Thu, Oct 20, 2022 at 04:42:23AM -0600, Joel Kulesza wrote:
> On Fri, Oct 7, 2022 at 8:39 AM Scott Kostyshak  wrote:
> 
> > On Thu, Oct 06, 2022 at 06:20:36AM -0600, Joel Kulesza wrote:
> >
> > > Please contact me with any comments, questions, or concerns.
> >
> > Very cool. Congrats!
> >
> > I do have questions, but no worries if you prefer to skip some of them :)
> >
> > 1. I forget whether you have 2.4.0dev set up, but if you do can you
> >compile your .lyx file (which I assume is in 2.3.x format) with
> >2.4.0dev and see if there are any differences (you can check with the
> >program 'diffpdf' for example, and set comparison to "appearance").
> >This is a combined test of lyx2lyx and of master's LaTeX output.
> >
> > 2. I see there are many authors. How many people actually edited the
> >.lyx file? What was your workflow to handle people working
> >simultaneously on such a large document? Did you use Git? Dropbox?
> >Did you use child documents?
> >
> > 3. How often did you need ERT? For example,
> >
> >  $ grep "begin_inset ERT" UserGuide.lyx | wc -l
> >  56
> >
> 
> Scott,
> 
> You ask some very interesting questions...  Thanks!
> 
> The manual you see is from TeXLive 2018 (locked into a particular version
> so the team uses a consistent version).  However, I just received a new
> computer with TeXLive 2022.  When I compare 2.4.0a3 versus 2.3.2 (the
> version used to prepare that document, again, locked at an older version
> across the team), I see notable differences.  The LuaLaTeX-produced 2.3.2
> document has 1084 pages and the LuaLaTeX-produced 2.4.0a3 document has 1073
> pages.  The difference appears to be the exclusion of content in 2.4.0a3
> where TeX code embedded in the child document program listing field is
> being processed differently between the two versions.  Also, there are a
> couple ERT processing issues of complicated index entries that lead to
> makeindex errors in 2.4.0a3 that are ignored in 2.3.2.  It's distressing
> that this differs but the fixes are straightforward and it's good to know
> about the issues.
> 
> Comparing 2.3.2 and 2.4.0a3 with TexLive 2018, I see the same, so it
> definitely comes down to how LyX is producing TeX.  However, one TeX-based
> difference we run into with such a complicated document is that including
> siunitx as we have before is no longer viable without memory tweaks.  I
> need to dive into this further.

Interesting! Thanks for those helpful notes. Let us know if you think
there might be a regression in LaTeX export.

> Regarding authors versus those touching the LyX file, there were about 16
> folks who modified the LyX file(s).  We use a git-centric, PR-review-based
> approach (with the Atlassian BitBucket tool).  This workflow is the reason
> that I tend to periodically raise the idea of significant end-of-line
> whitespace (with respect to comparing diffs, whitespace, and the
> frequent need to look at under-the-hood .lyx file code).  That said, I use
> a review process that involves looking at the code and resulting PDF.  I'm
> unsure of how this compares to my colleagues and how they use the code,
> PDF, or some combination.  Of course, I'm excited by Yuriy's recent
> interest and work on this.

Great! If Yuri's proposal is accepted, will that address the main issue
with end-of-line whitespace? If not, could you maybe attach a screenshot
of your diff tool where end-of-line whitespace makes it annoying to see
the real change?

> Regarding ERT, the answer surprises me.  We use parent-child documents and
> I see the "grep|wc" result of 1013.  I knew we used it, but that frequency
> is beyond what I expected (though perhaps sensible regarding how many
> cross-pointing index entries we have).  Note that we also have a ~700 line
> preamble.  Nevertheless, I'm unsure what we could meaningfully trim and,
> speaking for myself, it isn't unmanageable.

Nice! I don't think ERT is necessarily a problem. I was just curious.
Probably with some work on a module or local layout, we could reduce the
ERT in your document, but if the ERT isn't bothersome then it's likely
not worth the time.

> One remark, and something I need to construct an MWE from to then post to
> the tracker: there are periodically dialogs that accept TeX code (e.g., "~"
> or "\texttt") and some that misbehave (generally through literal
> interpretation) when supplied.  This appears to differ between 2.3.2 and
> 2.4.0a3.  Consistent and TeX-compliant behavior (in some manner) would be
> ideal for our use case.

Interesting. Indeed let me know if you have an MWE and I can see if it
is still an issue on current master.

> Thank you again for these good questions.  Sorry for the delayed response,
> but I wanted to provide a thorough analysis and description.

Thanks for all of those details!

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Thanks!

[Joel Kulesza]

On Fri, Oct 7, 2022 at 8:39 AM Scott Kostyshak  wrote:

> On Thu, Oct 06, 2022 at 06:20:36AM -0600, Joel Kulesza wrote:
>
> > Please contact me with any comments, questions, or concerns.
>
> Very cool. Congrats!
>
> I do have questions, but no worries if you prefer to skip some of them :)
>
> 1. I forget whether you have 2.4.0dev set up, but if you do can you
>compile your .lyx file (which I assume is in 2.3.x format) with
>2.4.0dev and see if there are any differences (you can check with the
>program 'diffpdf' for example, and set comparison to "appearance").
>This is a combined test of lyx2lyx and of master's LaTeX output.
>
> 2. I see there are many authors. How many people actually edited the
>.lyx file? What was your workflow to handle people working
>simultaneously on such a large document? Did you use Git? Dropbox?
>Did you use child documents?
>
> 3. How often did you need ERT? For example,
>
>  $ grep "begin_inset ERT" UserGuide.lyx | wc -l
>  56
>

Scott,

You ask some very interesting questions...  Thanks!

The manual you see is from TeXLive 2018 (locked into a particular version
so the team uses a consistent version).  However, I just received a new
computer with TeXLive 2022.  When I compare 2.4.0a3 versus 2.3.2 (the
version used to prepare that document, again, locked at an older version
across the team), I see notable differences.  The LuaLaTeX-produced 2.3.2
document has 1084 pages and the LuaLaTeX-produced 2.4.0a3 document has 1073
pages.  The difference appears to be the exclusion of content in 2.4.0a3
where TeX code embedded in the child document program listing field is
being processed differently between the two versions.  Also, there are a
couple ERT processing issues of complicated index entries that lead to
makeindex errors in 2.4.0a3 that are ignored in 2.3.2.  It's distressing
that this differs but the fixes are straightforward and it's good to know
about the issues.

Comparing 2.3.2 and 2.4.0a3 with TexLive 2018, I see the same, so it
definitely comes down to how LyX is producing TeX.  However, one TeX-based
difference we run into with such a complicated document is that including
siunitx as we have before is no longer viable without memory tweaks.  I
need to dive into this further.

Regarding authors versus those touching the LyX file, there were about 16
folks who modified the LyX file(s).  We use a git-centric, PR-review-based
approach (with the Atlassian BitBucket tool).  This workflow is the reason
that I tend to periodically raise the idea of significant end-of-line
whitespace (with respect to comparing diffs, whitespace, and the
frequent need to look at under-the-hood .lyx file code).  That said, I use
a review process that involves looking at the code and resulting PDF.  I'm
unsure of how this compares to my colleagues and how they use the code,
PDF, or some combination.  Of course, I'm excited by Yuriy's recent
interest and work on this.

Regarding ERT, the answer surprises me.  We use parent-child documents and
I see the "grep|wc" result of 1013.  I knew we used it, but that frequency
is beyond what I expected (though perhaps sensible regarding how many
cross-pointing index entries we have).  Note that we also have a ~700 line
preamble.  Nevertheless, I'm unsure what we could meaningfully trim and,
speaking for myself, it isn't unmanageable.

One remark, and something I need to construct an MWE from to then post to
the tracker: there are periodically dialogs that accept TeX code (e.g., "~"
or "\texttt") and some that misbehave (generally through literal
interpretation) when supplied.  This appears to differ between 2.3.2 and
2.4.0a3.  Consistent and TeX-compliant behavior (in some manner) would be
ideal for our use case.

Thank you again for these good questions.  Sorry for the delayed response,
but I wanted to provide a thorough analysis and description.

- Joel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Thanks!

[Joel Kulesza]

On Fri, Oct 7, 2022 at 6:42 AM Jean-Marc Lasgouttes <
lasgouttes.lyx@free.fr> wrote:

> Le 07/10/2022 à 13:51, Joel Kulesza a écrit :
> > Awesome, thank you for the feedback!
>
> You are welcome.
>
> BTW, is there feedback we are supposed to provide concerning the gitlab
> ticket migration? I am not pushing anything, it is just to make sure
> that you are not waiting on us and suffering from lack of interest.
>

JMarc et al.,

Yes, I'm still hoping for replies to my March 8 email (
https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg217242.html) and
more narrowly my developer-list July 14 email.  Notably, I didn't receive
any user accounts other than JMarc's to add to the private project to get
additional feedback (or I missed them and cannot find them, and I apologize
if that's the case).  Nevertheless, since March 8 and within the
developer-list thread following some additional discussion, I made the
example issue migration public (here:
https://gitlab.com/jkulesza/test_export_import/-/issues) but have received
no feedback subsequently.  So, I am "stuck" between my March 8th steps 2
and 3.

What I would propose at this point unless someone gives the feedback that
what's shown is unworkable, no good, etc., is to cleanup my migration
script, see if I can incorporate attachments and ensure issue number
correspondence, and prove out the process again.  If/when proven, we'll be
at the point of deciding whether to actually perform the migration, or
not.  Because of current work conditions, I'm unsure about the timing of
this, but unless I hear objections I'll pursue this plan.

I'm happy to hear any thoughts on this planned approach.

Thank you,
Joel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Thanks!

[Scott Kostyshak]

On Thu, Oct 06, 2022 at 06:20:36AM -0600, Joel Kulesza wrote:

> Please contact me with any comments, questions, or concerns.

Very cool. Congrats!

I do have questions, but no worries if you prefer to skip some of them :)

1. I forget whether you have 2.4.0dev set up, but if you do can you
   compile your .lyx file (which I assume is in 2.3.x format) with
   2.4.0dev and see if there are any differences (you can check with the
   program 'diffpdf' for example, and set comparison to "appearance").
   This is a combined test of lyx2lyx and of master's LaTeX output.

2. I see there are many authors. How many people actually edited the
   .lyx file? What was your workflow to handle people working
   simultaneously on such a large document? Did you use Git? Dropbox?
   Did you use child documents?

3. How often did you need ERT? For example,

 $ grep "begin_inset ERT" UserGuide.lyx | wc -l
 56

Thanks for sharing!

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Thanks!

[Jean-Marc Lasgouttes]

Le 07/10/2022 à 13:51, Joel Kulesza a écrit :

Awesome, thank you for the feedback!


You are welcome.

BTW, is there feedback we are supposed to provide concerning the gitlab 
ticket migration? I am not pushing anything, it is just to make sure 
that you are not waiting on us and suffering from lack of interest.


JMarc

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Thanks!

[Jean-Marc Lasgouttes]

Le 07/10/2022 à 13:51, Joel Kulesza a écrit :

Awesome, thank you for the feedback!


You are welcome.

BTW, is there feedback we are supposed to provide concerning the gitlab 
ticket migration? I am not pushing anything, it is just to make sure 
that you are not waiting on us and suffering from lack of interest.


JMarc

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Thanks!

[Joel Kulesza]

On Fri, Oct 7, 2022 at 2:36 AM Jean-Marc Lasgouttes 
wrote:

>
> > While I don't challenge you to read this 1,078-page document, I do
> > encourage you to read section 2.1.1, which describes the history of
> > Monte Carlo particle transport generally and the MCNP code
> > specifically.
>
> This is very interesting indeed. But since you ask for comments, I would
> point out that Buffon was a "comte" rather than a "compte"[*]. Laplace
> was one too, a simple "Buffon" would be enough.
>
> Awesome, thank you for the feedback!

- Joel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Thanks!

[Jean-Marc Lasgouttes]

Le 06/10/2022 à 14:20, Joel Kulesza a écrit :

LyX Developers,

The MCNP code recently released a total refresh of its theory and user 
manual in support of the upcoming version 6.3 release, which has been 
converted to be wholly reliant on LyX.  The manual is available at the 
top of https://mcnp.lanl.gov/manual.html 
 with older versions below it 
available for comparison.


Good work Joel (and others) !


While I don't challenge you to read this 1,078-page document, I do 
encourage you to read section 2.1.1, which describes the history of 
Monte Carlo particle transport generally and the MCNP code 
specifically.  


This is very interesting indeed. But since you ask for comments, I would 
point out that Buffon was a "comte" rather than a "compte"[*]. Laplace 
was one too, a simple "Buffon" would be enough.


JMarc

PS : actually, I considered the possibility that you meant "compte de 
Buffon" as "Buffon's count" (as in countng needles), but I did not find 
any reference to this name for his method.

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Thanks!

[Jean-Marc Lasgouttes]

Le 30/04/14 19:19, Wil a écrit :

To the LyX developers:

I've used LyX for six years as I've churned my way through my BS and MS
in mathematics.  I've given "intro to math typesetting with LyX" talks
to the math club at my university and I've evangelized it to anyone who
will listen.

I'm still discovering new ways to be impressed.  Recently I included a
graphviz dot file like it was a picture, and found that LyX already knew
how to handle it without me lifting a finger.  I was delighted.

Anyway, thanks for making my horrible handwriting irrelevant; my
homework has looked great since I started using LyX.  :)


You're welcome!

JMarc

Re: thanks

[Liviu Andronic]

Dear Derek
Thank you for the kind words.


On Wed, Sep 7, 2011 at 6:27 AM, Derek Lamb  wrote:
> I've been using LyX since ~2004 or so (version 1.3.x maybe?).  I've written 
> several papers, my master's and PhD theses, brief reports, software 
> documentation, and many grant proposals with it.  Over that time the 
> evolution has been steady and quite impressive.  The new features are useful 
> and mostly unobtrusive (though I'm still figuring out the 2.0 icon artwork!).
>
This can be easily reverted. Check Tools > Prefs > UI > Icon Set > Classic.

Regards
Liviu


> The changes serve a purpose instead of being change for change's sake.  LyX 
> today still has the same feel as it did back then, but so many things just 
> seem to work better now.  When I consider software evolution in general, and 
> open source software evolution in particular, I think of LyX as a great 
> example to follow.
>
> So, thanks, and keep up the great work!
>
> Derek



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: Thanks for outline mode

[Abdelrazak Younes]

On 11/09/2009 18:20, rgheck wrote:

On 09/11/2009 11:54 AM, Erez Yerushalmi wrote:

Hey, wow, I didn't even know about this feature.  I just tried it and it
works.  cool !

Thanks Steve for writing about it.
Yes, thanks for the developers amazing work!

To give credit where due, I think Abdel did most of this work, with 
help from elsewhere.


We shall also give credit to Martin who did the original LFUNs and 
Pavel, Jurgen and Vincent who did a lot of fine-tuning and polishing AFAIR.


Abdel.

Re: Thanks for outline mode

[rgheck]

On 09/11/2009 11:54 AM, Erez Yerushalmi wrote:

Hey, wow, I didn't even know about this feature.  I just tried it and it
works.  cool !

Thanks Steve for writing about it.
Yes, thanks for the developers amazing work!

   
To give credit where due, I think Abdel did most of this work, with help 
from elsewhere.


rh

Re: Thanks and Request for Feature

[Christian Ridderström]

On Thu, 23 Oct 2008, Sean Mullane wrote:

	This is my first time posting to this list. First, let me say that 
LyX has been a great tool for me - I do all my write-ups and homework 
sets in it now. It certainly makes LaTeX easier and faster to use. So 
keep up the good work!


	That said, I haven't found a way to include most cursive 
characters in math formulas. There is the \ell, \imath and \jmath, but 
that's it in terms of lower case cursive. Given that I study physics, 
characters like the cursive 'r' come up quite a bit. It would be nice if 
there were a whole cursive alphabet section like one sees for the greek 
letters.


I'm not especially well-versed in LaTeX, so it may be that this falls 
outside your realm, but if not it would be a much-appreciated feature.


Hi Sean,

I think you should try asking on the user's list, maybe someone there will 
know?  Otherwise it sounds like you should add it as a request for an 
enhancment in the Bugzilla system.


regards,
/Christian

--
Christian Ridderström, +46-8-768 39 44http://www.md.kth.se/~chr

Re: Thanks and Request for Feature

[rgheck]

Sean Mullane wrote:

No dice. using \mathcal on 'r' produces the dell operator. I don't think
 it works on lower case letters like it does on upper case ones

  

Right. I've seen that before, too. This must exist in some form.

rh

Re: Thanks and Request for Feature

[Sean Mullane]

No dice. using \mathcal on 'r' produces the dell operator. I don't think
 it works on lower case letters like it does on upper case ones

Sean

rgheck wrote:
> Sean Mullane wrote:
>> Hello,
>>
>> This is my first time posting to this list. First, let me say that
>> LyX
>> has been a great tool for me - I do all my write-ups and homework sets
>> in it now. It certainly makes LaTeX easier and faster to use. So keep up
>> the good work!
>>
>> That said, I haven't found a way to include most cursive
>> characters in
>> math formulas. There is the \ell, \imath and \jmath, but that's it in
>> terms of lower case cursive. Given that I study physics, characters like
>> the cursive 'r' come up quite a bit. It would be nice if there were a
>> whole cursive alphabet section like one sees for the greek letters.
>>
>>   
> I think what you want is \mathcal, which you can get by using whatever
> you'd ordinarily use for emphasis (by default, Ctrl-E) in mathmode.
> 
> rh
> 

Re: Thanks and Request for Feature

[rgheck]

Sean Mullane wrote:

Hello,

This is my first time posting to this list. First, let me say that LyX
has been a great tool for me - I do all my write-ups and homework sets
in it now. It certainly makes LaTeX easier and faster to use. So keep up
the good work!

That said, I haven't found a way to include most cursive characters in
math formulas. There is the \ell, \imath and \jmath, but that's it in
terms of lower case cursive. Given that I study physics, characters like
the cursive 'r' come up quite a bit. It would be nice if there were a
whole cursive alphabet section like one sees for the greek letters.

  
I think what you want is \mathcal, which you can get by using whatever 
you'd ordinarily use for emphasis (by default, Ctrl-E) in mathmode.


rh

Re: Thanks for the PDF options!

[Andre Poenitz]

On Mon, Oct 01, 2007 at 10:07:54AM +0200, Abdelrazak Younes wrote:
> I just tried it and it worked out of the box after removing everything I 
> had in the preamble (things that I never understood). Anyway, thanks a 
> lot to Pavel, Uwe, and anyone else who has participated; this is a great 
> feature!
> 
> Could we talk again about 1.6 timeline?*
> 
> Abdel.
> 
> * recurrent question I am going to ask every month or so :-)

All timelines end with "It's ready at Christmas".

But anyway, it looks like there's no real progress on the XML front, so
I, too, am tempted to remove "XML" from the official list of goals for
1.6 and let it be a quick "small features" release. 

Andre'

Re: Thanks for the PDF options!

[Bo Peng]

> > I actually had a look at this dialog, it does not seem to fit our
> > need. You know, we do *not* have a fixed number of things to assign
> > shortcuts for, and we need to categorize what we have (math, layout
> > etc). 
> >
> Right. Oh well.

But you know that I have a strong tendency to overshot my features...
In the end, maybe a simple multi-line view is enough. :-)

Bo

Re: Thanks for the PDF options!

[Richard Heck]

Bo Peng wrote:

I may have mentioned this before, but KDE applications all have this
kind of dialog. It's obviously KDE specific, but maybe it wouldn't be
too hard to adapt it. And wouldn't it be appropriate to borrow something
back from KDE? It's here:
http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/dialogs/kshortcutsdialog.*.


I actually had a look at this dialog, it does not seem to fit our
need. You know, we do *not* have a fixed number of things to assign
shortcuts for, and we need to categorize what we have (math, layout
etc). 
  

Right. Oh well.

Richard

Re: Thanks for the PDF options!

[Bo Peng]

> I may have mentioned this before, but KDE applications all have this
> kind of dialog. It's obviously KDE specific, but maybe it wouldn't be
> too hard to adapt it. And wouldn't it be appropriate to borrow something
> back from KDE? It's here:
> http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/dialogs/kshortcutsdialog.*.

I actually had a look at this dialog, it does not seem to fit our
need. You know, we do *not* have a fixed number of things to assign
shortcuts for, and we need to categorize what we have (math, layout
etc). 

Bo

Re: Thanks for the PDF options!

[Richard Heck]

Bo Peng wrote:

Could we talk again about 1.6 timeline?*


I am extremely busy recently but embedding should be done in a few
weeks (it is more or less done now). I have a shortcut editing dialog
in mind, which becomes more important after the recent Bold/C-B fight.
  
I may have mentioned this before, but KDE applications all have this 
kind of dialog. It's obviously KDE specific, but maybe it wouldn't be 
too hard to adapt it. And wouldn't it be appropriate to borrow something 
back from KDE? It's here: 
http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/dialogs/kshortcutsdialog.*.


Richard

Re: Thanks for the PDF options!

[Bo Peng]

> Could we talk again about 1.6 timeline?*

I am extremely busy recently but embedding should be done in a few
weeks (it is more or less done now). I have a shortcut editing dialog
in mind, which becomes more important after the recent Bold/C-B fight.
I will need about two month to do it.

Bo

Re: Thanks for lyx developers and users

[Abdelrazak Younes]

Jose' Matos wrote:
Thanks to the help of lyx developers and users, tips, advice, humour, no smile 
Fridays and so on, I have today officially delivered my thesis. It was a 
breeze with LyX. :-)


Congratulations to you soon-to-be Doctor Matos!

Abdel.

Re: Thanks for lyx developers and users

[Jean-Marc Lasgouttes]

> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:

Jose'>   Well not quite, the Viva (defense, whatever...) will be in a
Jose'> couple of months, but as usual arriving here means that the
Jose'> task is almost finished.

Congratulation, Jose'! Some neverending tasks do end, after all...

Jose'>   I live in the right hemisphere, so that is not a problem. ;-)

The right hemisphere of whose brain?

JMarc

Re: Thanks for lyx developers and users

[Martin Vermeer]

On Mon, 31 Jul 2006 19:39:20 +0100 Jose' Matos <[EMAIL PROTECTED]> wrote:

> Thanks to the help of lyx developers and users, tips, advice, humour,
> no smile 
> Fridays and so on, I have today officially delivered my thesis. It was
> a 
> breeze with LyX. :-)
> 
>   Thanks guys (and gals),
> -- 
> José Abílio
> 

Congratulations José. It's a once in a lifetime thing...

- Martin

Re: Thanks for lyx developers and users

[Jose' Matos]

On Tuesday 01 August 2006 22:50, [EMAIL PROTECTED] wrote:
> Congratulations.

  Thanks. :-)

> Finishing a thesis is like lifting a heavy weight from 
> your stomach.

  I am in such a good mood that I have almost finished the support for lyx2lyx 
to formats from lyx 0.7 and 0.8. :-)

  Does anyone has lyx 0.6 and/or 0.5 at hand? ;-)

> Cheers,
> Charles

-- 
José Abílio

Re: Thanks for lyx developers and users

[cmiramon]

Jose' Matos wrote:
> I have today officially delivered my thesis. It

Congratulations. Finishing a thesis is like lifting a heavy weight from your
stomach.

Cheers,
Charles

Re: Thanks for lyx developers and users

[Georg Baum]

Am Montag, 31. Juli 2006 20:46 schrieb Lars Gullik Bjønnes:
> Jose' Matos <[EMAIL PROTECTED]> writes:
> 
> | Thanks to the help of lyx developers and users, tips, advice, humour, 
no smile 
> | Fridays and so on, I have today officially delivered my thesis. It was 
a 
> | breeze with LyX. :-)

Congratulations!

> Very good. Now get your python conversion tools cranking. Unicode
> branch is ready for lyx2lyx magic.

Looking forward to a fully working unicode LyX when I am back ;-)


Georg

Re: Thanks for lyx developers and users

[Edwin Leuven]

Lars Gullik Bjønnes wrote:

Stop that!


ok

Come help in the wondrous world of unicode. You can pick a char for 
your very own and cuddle it to your hearths desire.


fortunately, being dutch, latin1 does it for me. but i must admit that 
you make it sound terribly tempting


hadet!

;-)

Re: Thanks for lyx developers and users

[Lars Gullik Bjønnes]

Jose' Matos <[EMAIL PROTECTED]> writes:

| On Monday 31 July 2006 19:46, Lars Gullik Bjønnes wrote:
| > Very good. Now get your python conversion tools cranking. Unicode
| > branch is ready for lyx2lyx magic.
| 
|   I am thinking about that and also about this (if you still remember it) 
| http://www.mail-archive.com/lyx-devel%40lists.lyx.org/msg22164.html

I think we should postpone that until we have an xml format, and then
we should just forget about it and use xsl-transformations to create
the other formats. 

My next project after this unicode thingie will be xml. (Which is
mostly finished anyway...)

-- 
Lgb

Re: Thanks for lyx developers and users

[Jose' Matos]

On Monday 31 July 2006 19:51, Edwin Leuven wrote:
> Jose' Matos wrote:
> > Thanks to the help of lyx developers and users, tips, advice, humour, no
> > smile Fridays and so on, I have today officially delivered my thesis.
>
> welcome doctor, congratulations!

  Well not quite, the Viva (defense, whatever...) will be in a couple of 
months, but as usual arriving here means that the task is almost finished.

> > It was a breeze with LyX. :-)
>
> even without unicode?

  I live in the right hemisphere, so that is not a problem. ;-)

  All Portuguese symbols fit into latin-1.

> (just teasin' lars ;-)

  I will lend him a hand now. :-)

> >   Thanks guys (and gals),

-- 
José Abílio

Re: Thanks for lyx developers and users

[Jose' Matos]

On Monday 31 July 2006 19:46, Lars Gullik Bjønnes wrote:
> Very good. Now get your python conversion tools cranking. Unicode
> branch is ready for lyx2lyx magic.

  I am thinking about that and also about this (if you still remember it) 
http://www.mail-archive.com/lyx-devel%40lists.lyx.org/msg22164.html

> --
> Lgb

-- 
José Abílio

Re: Thanks for lyx developers and users

[Lars Gullik Bjønnes]

Edwin Leuven <[EMAIL PROTECTED]> writes:

| Jose' Matos wrote:
| > Thanks to the help of lyx developers and users, tips, advice,
| > humour, no smile Fridays and so on, I have today officially
| > delivered my thesis.
| 
| welcome doctor, congratulations!
| 
| > It was a breeze with LyX. :-)
| 
| even without unicode?
| 
| (just teasin' lars ;-)

Stop that!

Come help in the wondrous world of unicode. You can pick a char for
your very own and cuddle it to your hearths desire.

-- 
Lgb

Re: Thanks for lyx developers and users

[Edwin Leuven]

Jose' Matos wrote:
Thanks to the help of lyx developers and users, tips, advice, humour, no smile 
Fridays and so on, I have today officially delivered my thesis.


welcome doctor, congratulations!


It was a breeze with LyX. :-)


even without unicode?

(just teasin' lars ;-)


  Thanks guys (and gals),

Re: Thanks for lyx developers and users

[Lars Gullik Bjønnes]

Jose' Matos <[EMAIL PROTECTED]> writes:

| Thanks to the help of lyx developers and users, tips, advice, humour, no 
smile 
| Fridays and so on, I have today officially delivered my thesis. It was a 
| breeze with LyX. :-)

Very good. Now get your python conversion tools cranking. Unicode
branch is ready for lyx2lyx magic.

-- 
Lgb

Re: Thanks!!

[christian . ridderstrom]

On Mon, 12 Jun 2006, Jean-Marc Lasgouttes wrote:


"Graham" == Graham Watts <[EMAIL PROTECTED]> writes:


Graham> PS: I realize that this is not necessarily the correct place
Graham> to send this message and apologize if this has upset anyone. I
Graham> simply wanted to contact the people actively developing Lyx as
Graham> they are the ones I wish to thank.

I do not think anyone here will be upset by a bit of ego boosting :)


Hardly, I'm sure the developers appreciate someone who doesn't complain 
about bugs and missing features for once ;-)


Congrats on your degree!
/Christian

PS. There's a page on the wiki where you could list the kind of documents 
you've written using LyX.

http://wiki.lyx.org/LyX/ProducedPublications

Or you can just give praise on this page

http://wiki.lyx.org/LyX/Praise

Then some people complain that LyX doesn't do their laundry here ;-)

http://wiki.lyx.org/LyX/Complaints


--
Christian Ridderström, +46-8-768 39 44   http://www.md.kth.se/~chr

Re: Thanks!!

[Jean-Marc Lasgouttes]

> "Graham" == Graham Watts <[EMAIL PROTECTED]> writes:

Graham> PS: I realize that this is not necessarily the correct place
Graham> to send this message and apologize if this has upset anyone. I
Graham> simply wanted to contact the people actively developing Lyx as
Graham> they are the ones I wish to thank.

I do not think anyone here will be upset by a bit of ego boosting :)

Congratulations to you.

JMarc

Re: Thanks

[John Levon]

On Thu, Apr 04, 2002 at 02:18:37PM +0200, Juergen Spitzmueller wrote:

> BTW: Is the xforms AskForText dialog supposed to be replaced by a self 
> created dialog eventually?

I don't know. I half-finished a patch to do this for insert label, some
time ago

john

-- 
"I never understood what's so hard about picking a unique
 first and last name - and not going beyond the 6 character limit."
- Toon Moene

Re: Thanks

[Angus Leeming]

On Thursday 04 April 2002 1:18 pm, Juergen Spitzmueller wrote:
> John Levon wrote:
> > > Then I wonder on which popups he is talking about.
> >
> > Insert label ? One of Michael S's bete noires ...
>
> I suspected this too. And it is very reasonable: all bad things are
> xforms things anyway ;-)
>
> BTW: Is the xforms AskForText dialog supposed to be replaced by a self
> created dialog eventually?
>
> Juergen.

I believe we decided not to use any of the xforms goodies. Eventually.
Angus

Re: Thanks

[Juergen Spitzmueller]

John Levon wrote:
> > Then I wonder on which popups he is talking about.
>
> Insert label ? One of Michael S's bete noires ...

I suspected this too. And it is very reasonable: all bad things are 
xforms things anyway ;-)

BTW: Is the xforms AskForText dialog supposed to be replaced by a self 
created dialog eventually?

Juergen.

Re: Thanks

[John Levon]

On Thu, Apr 04, 2002 at 12:16:17PM +0200, Juergen Spitzmueller wrote:

> Then I wonder on which popups he is talking about.

Insert label ? One of Michael S's bete noires ...

john

-- 
"I never understood what's so hard about picking a unique
 first and last name - and not going beyond the 6 character limit."
- Toon Moene

Re: Thanks

[Juergen Spitzmueller]

Andre Poenitz wrote:
> > "In popups, the "Clear"[?] button

> "Delete".

Then I wonder on which popups he is talking about.

Juergen.

Re: Thanks

[Andre Poenitz]

On Thu, Apr 04, 2002 at 11:55:58AM +0200, Juergen Spitzmueller wrote:
> "In popups, the "Clear"[?] button

"Delete".

Andre'

-- 
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)

Re: Thanks

[Juergen Spitzmueller]

Antonio Gulino wrote:
> PS: article, in german, about LyX
> http://www.unix-open.de/aktuelle-ausgabe/03_2002/unix_0302_053.html

A nice review btw. A bad translation for all non-german people:

"Das Paket "LyX" kann für die Textverarbeitung eine große Bereicherung 
sein, denn es korrigiert die derzeitige Entwicklung der aktuellen 
Office-Programme: Immer mehr Funktionen arbeiten unzulänglich und 
werden auch durch Plagegeister in Gestalt von Assistenten nicht besser."

"The package "LyX" can be a big gain for text processing, for it does 
not follow the way of recent office applications. More and more 
features don't work correctly, and pests coming as wizards don't make 
this better."

And something more critical:

"In Dialogen zerrt die Entfernen-Taste sehr an den Nerven. Sie verhält 
sich wie Backspace, und nach ausgiebigem Markieren ist manchmal ein 
Absturz unausweichlich."

"In popups, the "Clear"[?] button is very annoying. It behaves like the 
backspace key, and after marking the text several times, a crash is 
often inescapable."

Regards,
Juergen.

Re: Thanks

[Pawan Kumar]

Hi will also say thanks to everyone if someone could help me to
unsubscribe it.

i tried lot of times by sending mail to [EMAIL PROTECTED]
Is there any other way to do it??
bye
all the best lyx users
pawan

On Wed, 3 Apr 2002, Antonio Gulino wrote:

> I say "Thanks" to the LyX-Team,
> because I finished my graduate thesis written with LyX
>
> I say "Thanks" to the help on the users list,
> because I find many solutions.
>
> I say thanks to everybody,
> because I have written the thesis *about* LyX (and Open Source)
>
> "Lo sviluppo del software in ambito Open Source: il caso LyX"
> "OpenSource-Software developement: LyX"
>
> The thesis is in italian.
> http://tomi.freeweb.supereva.it/lyx/
>
> bye
> Antonio
>
> PS: article, in german, about LyX
> http://www.unix-open.de/aktuelle-ausgabe/03_2002/unix_0302_053.html
> in Unix Open, Mars 2002, pages 53-56
> by Karlheinz Günster
>

Re: Thanks

[Lars Gullik Bjønnes]

Antonio Gulino <[EMAIL PROTECTED]> writes:

| I say "Thanks" to the LyX-Team,
| because I finished my graduate thesis written with LyX
>
| I say "Thanks" to the help on the users list,
| because I find many solutions.
>
| I say thanks to everybody,
| because I have written the thesis *about* LyX (and Open Source)
>
| "Lo sviluppo del software in ambito Open Source: il caso LyX"
| "OpenSource-Software developement: LyX"
>
| The thesis is in italian.
| http://tomi.freeweb.supereva.it/lyx/

Quite interesting even if I didn't understand a "puck" :-)

-- 
Lgb

Re: Thanks

[Angus Leeming]

It was a pleasure! Thanks for the thanks.
Angus

On Wednesday 24 January 2001 21:09, Micha H. Werner wrote:
> Hello, 
> 
> a couple of weeks ago I reported some problems in interaction between 
> LyX and pybliographer. I was _very_ impressed how fast Angus and Jean-
> Marc answered and solved the problems. It really was an convincing 
> demonstration of the efficiency of open source development. I wish I 
> could help you developing LyX, but since I'm just a stupid user, I 
> can only give you comments and feedback. 
> Thanks for your great work! 
> 
> Micha H. Werner
> ___
> 
> Micha H. Werner
> Eberhard Karls Universität Tuebingen
> Lehrstuhl für Ethik in der Medizin 
> Keplerstrasse 15
> D-72074 Tuebingen
> 
> privat:
> 
> Gosslerstrasse 18
> D-12161 Berlin 
> Tel.: +49-30-8516908 oder 0162-5941268
> 
> Homepage:
> http://user.berlin.de/~m.werner/
> 
> Homepage des Forschungsprojekts:
> http://www.izew.uni-tuebingen.de/medizinethik/projekte/deutsch/
> 
> E-mail:
> [EMAIL PROTECTED]

Re: Thanks for LyX

[Amir Karger]

On Fri, Jan 19, 2001 at 10:14:55PM +, Carlos A. M. dos Santos wrote:
> 
> Dear sirs
> 
> Doped by litres of cofee, and after three weeks working like a horse, I
> finally submited my master thesys today. 
> 

Congratulations!

I hope to be the next to send a thank-you note to the list... (March,
maybe? Wish me luck.)

-Amir

Re: Thanks for LyX

[Jose Abilio Oliveira Matos]

On Fri, Jan 19, 2001 at 10:14:55PM +, Carlos A. M. dos Santos wrote:
> 
> Dear sirs
> 
> Doped by litres of cofee, and after three weeks working like a horse, I
> finally submited my master thesys today. Without LyX, this probably could
> not happen, or perhaps I were submited to the humiliation of using a
> software that treats me as an idiot: MS-Word.
> 
> There are no words to explain my gratitude to each one of the developers
> of this wonderful tool that LyX is, and that I heve been using with
> pleasure almost daily for the last three years.
> 
>  All I can say is THANKS, THANKS, THANKS, THANKS, THANKS, THANKS, THANKS,
> THANKS, THANKS, THANKS, THANKS!

  On behalf of LyX team congratulations.
  
  Parabens Carlos :-)
  
> Now going to bed.
>   
> --
> Carlos A. M. dos Santos
> 
> Federal University of Pelotas Meteorological Research Center
> Av. Ildefonso Simoes Lopes 2791   Pelotas, RS, Brasil, CEP 96060-290
> WWW: http://www.cpmet.ufpel.tche.br   RENPAC (X.25): 153231641
> Phone: +55 53 277-6767FAX: +55 53 277-6722

-- 
José

Re: Thanks!

[Jose Abilio Oliveira Matos]

On Fri, Oct 08, 1999 at 04:35:16PM -0400, Luis Villa wrote:
> Several months ago, I sent a note to this list asking about DocBook 
> support in Lyx, and you all said "it'll be here soon." Well, it is here 
> and it is great. You guys have put out a great product, and are to be 
> commended. Thanks a bunch for all the hard work.

  It is nice to hear that :)
  
> Sincerely,
> Luis Villa
> 
> ###
> 
>  Profanity is the one language that all programmers understand.
> -Anonymous
> 
> ###

-- 
José

Re: Thanks + Printer problem

[Mate Wierdl]

   
   dvips: ! no config file for printer `lp'

The problem is that dvips is not configured to use the default
printer.

Since you probably are running teTeX, you could use texconfig to make
a config file for lp.

Mate