Guys,
Am recently a convert (though use the win32 port from Ruurd Reitsma)
from word (to write my PhD thesis!!!) and have a wish...
Why should I need to add labels to sections, subsections
subsubsections (and even figures, tables, etc) before being able to
cross reference them. Surely using
On Mon, Jun 30, 2003 at 01:19:07PM +0100, Dan Owen wrote:
Guys,
Am recently a convert (though use the win32 port from Ruurd Reitsma)
from word (to write my PhD thesis!!!) and have a wish...
Why should I need to add labels to sections, subsections
subsubsections (and even figures,
*) in the list of reference points (figures, etc also).
To late for 1.4?
Cheers
Dan.
-Original Message-
From: Andre Poenitz [mailto:[EMAIL PROTECTED]
Sent: 30 June 2003 13:28
To: Dan Owen
Cc: [EMAIL PROTECTED]
Subject: Re: wish list: cross-referencing
On Mon, Jun 30, 2003 at 01:19:07PM +0100
On Mon, Jun 30, 2003 at 01:31:50PM +0100, Dan Owen wrote:
OK, now your on the hook!...
*shrug*
I already found this annoying myself.
I use a lot of ERT inserts which manual label verbatim, for these I
don't mind manually cross-referencing...
But when I want to cross reference a section, I
available in Lyx 1.4Certainly not.
Ace!
Do you want everything labeled all the time?
Suggestion. Referencing to the 'Cross reference' dialog box current in
lyx 1.3.2...
Below Document and above Available references in selected document
have two radio options (one MUST be selected).
Guys,
Am recently a convert (though use the win32 port from Ruurd Reitsma)
from word (to write my PhD thesis!!!) and have a wish...
Why should I need to add labels to sections, subsections &
subsubsections (and even figures, tables, etc) before being able to
cross reference them. Surely using
On Mon, Jun 30, 2003 at 01:19:07PM +0100, Dan Owen wrote:
> Guys,
>
> Am recently a convert (though use the win32 port from Ruurd Reitsma)
> from word (to write my PhD thesis!!!) and have a wish...
>
> Why should I need to add labels to sections, subsections &
> subsubsections (and even
tion*) in the list of reference points (figures, etc also).
To late for 1.4?
Cheers
Dan.
-Original Message-
From: Andre Poenitz [mailto:[EMAIL PROTECTED]
Sent: 30 June 2003 13:28
To: Dan Owen
Cc: [EMAIL PROTECTED]
Subject: Re: wish list: cross-referencing
On Mon, Jun 30, 2003 at 01:19:07PM +
On Mon, Jun 30, 2003 at 01:31:50PM +0100, Dan Owen wrote:
> OK, now your on the hook!...
*shrug*
I already found this annoying myself.
> I use a lot of ERT inserts which manual label verbatim, for these I
> don't mind manually cross-referencing...
>
> But when I want to cross reference a
>available in Lyx 1.4Certainly not.
Ace!
>Do you want everything labeled all the time?
Suggestion. Referencing to the 'Cross reference' dialog box current in
lyx 1.3.2...
Below "Document" and above "Available references in selected document"
have two radio options (one MUST be selected).
adi == adi mailbox [EMAIL PROTECTED] writes:
adi c) Some of ERT commands do not work with lyx but work fine if the
adi file is converted first to latex [see b) above]. For example the
adi following lyx code:
[...]
adi The output if viewed in lyx is different compared with the case
adi when the
> "adi" == adi mailbox <[EMAIL PROTECTED]> writes:
adi> c) Some of ERT commands do not work with lyx but work fine if the
adi> file is converted first to latex [see b) above]. For example the
adi> following lyx code:
[...]
adi> The output if viewed in lyx is different compared with the case
Hi!
First I would like to congratulate you for this
product. I enjoyed working with it.
Second, I have a wish list to improve Lyx.
a) Instead of pallet, I think configurable toolbars
are much easier to work with.
b) I noticed that the layout conversion of a file to
pdf can be different from
Hi!
First I would like to congratulate you for this
product. I enjoyed working with it.
Second, I have a wish list to improve Lyx.
a) Instead of pallet, I think configurable toolbars
are much easier to work with.
b) I noticed that the layout conversion of a file to
pdf can be different from
Hello,
I am not subscribed to lyx-devel, but I was advised to sent my small
wish list here. Sorry, if these are already been mentioned, worked on,
or already solved, but it is really difficult for an ordinary user to
follow devel efforts..
Current version I use is 1.1.6fix3 on solaris8.
I
Frank K. Gurkaynak wrote:
That's it. Please, please please better minipage support... did I say
please ??
LyX 1.2.0 will have a totally new minipage support, which is indeed
much better than the hack in 1.1.6
Regards,
Juergen.
Hello,
I am not subscribed to lyx-devel, but I was advised to sent my small
wish list here. Sorry, if these are already been mentioned, worked on,
or already solved, but it is really difficult for an ordinary user to
follow devel efforts..
Current version I use is 1.1.6fix3 on solaris8.
I
Frank K. Gurkaynak wrote:
> That's it. Please, please please better minipage support... did I say
> please ??
LyX 1.2.0 will have a totally new minipage support, which is indeed
much better than the hack in 1.1.6
Regards,
Juergen.
On Thu, Dec 20, 2001 at 01:59:42PM -0400, John Janmaat wrote:
More for the wish list,
Integrate a bibtex reference manager.
Why ? We already support the lyxserver so managers like gbib can
insert references into lyx. I don't think we need to go beyond that
level of integration ...
regards
On Thu, Dec 20, 2001 at 01:59:42PM -0400, John Janmaat wrote:
> More for the wish list,
>
> Integrate a bibtex reference manager.
Why ? We already support the lyxserver so managers like gbib can
insert references into lyx. I don't think we need to go beyond that
level of in
More for the wish list,
Integrate a bibtex reference manager. I have written one in Java, that
is available on CTAN. It is called JavaBib. It is mostly functional,
to the point that I am using it for all my reference management. I do
not have the time to further develop it, and was unable
More for the wish list,
Integrate a bibtex reference manager. I have written one in Java, that
is available on CTAN. It is called JavaBib. It is mostly functional,
to the point that I am using it for all my reference management. I do
not have the time to further develop it, and was unable
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel Content-Type: text/plain; charset=us-ascii On Tue, May 02, 2000
Dekel at 05:02:23PM +0200, Jean-Marc Lasgouttes wrote:
It would be useful if the menu were hierarchical, in which case the
TOC browser should go away.
Dekel I've changed the
On Wed, May 10, 2000 at 02:08:08PM +0200, Jean-Marc Lasgouttes wrote:
Dekel 2. Sort the labels in the Insert Reference Dialog/Refs menu
That's nice. Is it possible to make it optional (a check box in the
popup?) for people who prefer them in docuemnt order?
Done.
I've also added
1.
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> Content-Type: text/plain; charset=us-ascii On Tue, May 02, 2000
Dekel> at 05:02:23PM +0200, Jean-Marc Lasgouttes wrote:
>> It would be useful if the menu were hierarchical, in which case the
>> TOC browser should go away.
Dekel>
On Wed, May 10, 2000 at 02:08:08PM +0200, Jean-Marc Lasgouttes wrote:
>
> Dekel> 2. Sort the labels in the Insert Reference Dialog/Refs menu
>
> That's nice. Is it possible to make it optional (a check box in the
> popup?) for people who prefer them in docuemnt order?
Done.
I've also added
1.
On Tue, May 02, 2000 at 05:02:23PM +0200, Jean-Marc Lasgouttes wrote:
It would be useful if the menu were hierarchical, in which case the
TOC browser should go away.
I've changed the ToC menu to be hierarchical.
Besides the new ToC Refs menus, the patch does other things:
1. Editable labels.
On Tue, May 02, 2000 at 05:02:23PM +0200, Jean-Marc Lasgouttes wrote:
> It would be useful if the menu were hierarchical, in which case the
> TOC browser should go away.
I've changed the ToC menu to be hierarchical.
Besides the new ToC & Refs menus, the patch does other things:
1. Editable
On Wed, May 03, 2000 at 10:05:57AM +1000, Allan Rae wrote:
I'd rather we improved the integration of external programs than try to
duplicate their capabilities into LyX. It should be possible using XTL in
LyX and some corresponding externalization support in the external
programs to get/set
On Wed, May 03, 2000 at 10:05:57AM +1000, Allan Rae wrote:
> I'd rather we improved the integration of external programs than try to
> duplicate their capabilities into LyX. It should be possible using XTL in
> LyX and some corresponding externalization support in the external
> programs to
Allan Rae [EMAIL PROTECTED] writes:
| A different colour with the pretty 3d boxes that we had in the old tree.
| (I know, the 3d boxes are dependent on the Painter so I'll have to wait
| for those)
What do you mean? We have been using the Painter for some months
now...
Lgb
Allan Rae [EMAIL PROTECTED] writes:
| I (one day) want to add the option of document scope selection of a
| citation package (harvard.sty etc.) and then have a corresponding menu in
| the citation dialog for the various forms of citation that package
| provides (citeyear, citeauthor and so on).
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Allan Rae [EMAIL PROTECTED] writes: | A different
Lars colour with the pretty 3d boxes that we had in the old tree. |
Lars (I know, the 3d boxes are dependent on the Painter so I'll have
Lars to wait | for those)
Lars What do you
Allan Rae <[EMAIL PROTECTED]> writes:
| A different colour with the pretty 3d boxes that we had in the old tree.
| (I know, the 3d boxes are dependent on the Painter so I'll have to wait
| for those)
What do you mean? We have been using the Painter for some months
now...
Lgb
Allan Rae <[EMAIL PROTECTED]> writes:
| I (one day) want to add the option of document scope selection of a
| citation package (harvard.sty etc.) and then have a corresponding menu in
| the citation dialog for the various forms of citation that package
| provides (citeyear, citeauthor and so
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Allan Rae <[EMAIL PROTECTED]> writes: | A different
Lars> colour with the pretty 3d boxes that we had in the old tree. |
Lars> (I know, the 3d boxes are dependent on the Painter so I'll have
Lars> to wait | for those)
Lars>
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel I've already suggested this idea (however, I think that the ToC
Dekel should be "flat" if there is small enough).
Yes, there may be some threshold (the same would hold for submenus).
Currently, the menu for the UserGuide is not usable.
On 3 May 2000, Jean-Marc Lasgouttes wrote:
Dekel I put it on the left side in order to leave enough room for
Dekel long lines in the menu. However, this can be changed easily.
Yes. And then what about the TOC popup? Should it be removed?
In a word: No.
Maybe I'm the only one; but it's
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> I've already suggested this idea (however, I think that the ToC
Dekel> should be "flat" if there is small enough).
Yes, there may be some threshold (the same would hold for submenus).
Currently, the menu for the UserGuide is not
On 3 May 2000, Jean-Marc Lasgouttes wrote:
> Dekel> I put it on the left side in order to leave enough room for
> Dekel> long lines in the menu. However, this can be changed easily.
>
> Yes. And then what about the TOC popup? Should it be removed?
In a word: No.
Maybe I'm the only one; but
"Amir" == Amir Karger [EMAIL PROTECTED] writes:
Amir IMO, there shouldn't be lots of different ways of looking at the
Amir TOC. Seems like overkill and too many features. Why have a
Amir separate menu of the TOC when you can get it with keys,
Amir mouseclick, or menu selection?
It would be
IMO, there shouldn't be lots of different ways of looking at the TOC. Seems
like overkill and too many features. Why have a separate menu of the TOC
when you can get it with keys, mouseclick, or menu selection?
-Amir
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel OK. I've changed my patch to (2). The attached patch contains
Dekel both ToC Refs menus (and it also simplifies existing code).
Hi Dekel. I really like the idea of this patch...
Some comments:
- could the TOC menu be hierarchical (with
On Mon, 1 May 2000, Dekel Tsur wrote:
On Mon, May 01, 2000 at 12:41:03PM +1000, Allan Rae wrote:
What did you have in mind for the citation popup?
[...]
In addition one change I've been meaning to do for ages which should be
extremely simple is to change the combox operation so that if
On Mon, May 01, 2000 at 07:11:33PM -0300, Garst R. Reese wrote:
or by typing "M-e t".
Duh,
But in that case why not just have the TOC on the menu do the same
thing?
Are there key-bindings for TOC and REF? e.g., F10-T F10-R
M-t and M-r
On Tue, May 02, 2000 at 06:06:55PM +1000, Allan Rae wrote:
That's what pybliographer, barracuda and tkbib among others are all for.
It would be nice if they could insert multiple references however I think
they only insert one at a time at the moment.
I'm aware of these programs, but I think
On Tue, May 02, 2000 at 10:54:40AM -0400, Amir Karger wrote:
IMO, there shouldn't be lots of different ways of looking at the TOC. Seems
like overkill and too many features. Why have a separate menu of the TOC
when you can get it with keys, mouseclick, or menu selection?
Using my ToC menu is
On Tue, 2 May 2000, Dekel Tsur wrote:
On Tue, May 02, 2000 at 06:06:55PM +1000, Allan Rae wrote:
That's what pybliographer, barracuda and tkbib among others are all for.
It would be nice if they could insert multiple references however I think
they only insert one at a time at the moment.
Jean-Marc Lasgouttes wrote:
- Now that labels are editable, there should maybe be something like
'label:' in their box, so that they are really different from refs.
Of course, a small icon would be nice, but it might be a bit
difficult.
JMarc
I just tested this great new feature
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
Amir> IMO, there shouldn't be lots of different ways of looking at the
Amir> TOC. Seems like overkill and too many features. Why have a
Amir> separate menu of the TOC when you can get it with keys,
Amir> mouseclick, or menu selection?
It
IMO, there shouldn't be lots of different ways of looking at the TOC. Seems
like overkill and too many features. Why have a separate menu of the TOC
when you can get it with keys, mouseclick, or menu selection?
-Amir
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> OK. I've changed my patch to (2). The attached patch contains
Dekel> both ToC & Refs menus (and it also simplifies existing code).
Hi Dekel. I really like the idea of this patch...
Some comments:
- could the TOC menu be
On Mon, 1 May 2000, Dekel Tsur wrote:
> On Mon, May 01, 2000 at 12:41:03PM +1000, Allan Rae wrote:
> > What did you have in mind for the citation popup?
> [...]
> > In addition one change I've been meaning to do for ages which should be
> > extremely simple is to change the combox operation so
On Mon, May 01, 2000 at 07:11:33PM -0300, Garst R. Reese wrote:
> > or by typing "M-e t".
> Duh,
> But in that case why not just have the TOC on the menu do the same
> thing?
> Are there key-bindings for TOC and REF? e.g., F10-T F10-R
M-t and M-r
On Tue, May 02, 2000 at 06:06:55PM +1000, Allan Rae wrote:
> That's what pybliographer, barracuda and tkbib among others are all for.
> It would be nice if they could insert multiple references however I think
> they only insert one at a time at the moment.
I'm aware of these programs, but I
On Tue, May 02, 2000 at 10:54:40AM -0400, Amir Karger wrote:
> IMO, there shouldn't be lots of different ways of looking at the TOC. Seems
> like overkill and too many features. Why have a separate menu of the TOC
> when you can get it with keys, mouseclick, or menu selection?
Using my ToC menu
On Tue, 2 May 2000, Dekel Tsur wrote:
> On Tue, May 02, 2000 at 06:06:55PM +1000, Allan Rae wrote:
> > That's what pybliographer, barracuda and tkbib among others are all for.
> > It would be nice if they could insert multiple references however I think
> > they only insert one at a time at the
Jean-Marc Lasgouttes wrote:
> - Now that labels are editable, there should maybe be something like
> 'label:' in their box, so that they are really different from refs.
> Of course, a small icon would be nice, but it might be a bit
> difficult.
>
> JMarc
I just tested this great new
On Sun, Apr 30, 2000 at 07:39:43PM -0300, Garst R. Reese wrote:
Just tested it. It's really nice to be able to get to TOC without having
to find it in the doc.
You can open the ToC popup using the "Edit-Table of contents" menu,
or by typing "M-e t".
On Sun, Apr 30, 2000 at 07:39:43PM -0300, Garst R. Reese wrote:
> Just tested it. It's really nice to be able to get to TOC without having
> to find it in the doc.
You can open the ToC popup using the "Edit->Table of contents" menu,
or by typing "M-e t".
I'll get this in before you folks head off to your FUND'EM or what ever
you are calling it this year. I'm much to envious to remember.
I would like to be able to define minipage setups in a style file so
that I could get to it the same way I get to Chapter etc. i.e., I want
to say that I want
On Sun, Apr 30, 2000 at 01:15:12AM +0300, Dekel Tsur wrote:
Yes, but I think that the style I use is quite clear.
To refresh your memory, I've created a procedure
(1) void LyXParagraph::String(string s)
that writes the paragraph into the string s.
The alternative is
(2) string
"Asger K. Alstrup Nielsen" [EMAIL PROTECTED] writes:
| The alternative is
| (2) string LyXParagraph::String()
| that returns a string from the paragraph.
|
| Do you really think that (2) is clearer/better than (1) ?
| Should I stay with (1) ?
|
| If the method produces a new string, and
Jules Bean [EMAIL PROTECTED] writes:
| (2) says what it means. If efficiency is bothering you, you can save a
| copy by making th procedure return a string.
No you can't unless you have a static string in the method, or
returning a temporary which is invalid.
Lgb
On Sun, Apr 30, 2000 at 03:27:28AM -0300, Garst R. Reese wrote:
I also noticed that if I set Section Number Depth to -1, clicking on an
entry in the TOC takes me to the top of the document instead of the
desired place.
I've rewritten the TOC code, and fixed this bug as a side effect :)
I'll
Dekel Tsur wrote:
On Sun, Apr 30, 2000 at 03:27:28AM -0300, Garst R. Reese wrote:
I also noticed that if I set Section Number Depth to -1, clicking on an
entry in the TOC takes me to the top of the document instead of the
desired place.
I've rewritten the TOC code, and fixed this
On Sun, Apr 30, 2000 at 12:26:43AM +0200, Asger K. Alstrup Nielsen wrote:
(1) void LyXParagraph::String(string s)
that writes the paragraph into the string s.
The alternative is
(2) string LyXParagraph::String()
that returns a string from the paragraph.
This is what (1) could
Dekel Tsur wrote:
On Sun, Apr 30, 2000 at 12:26:43AM +0200, Asger K. Alstrup Nielsen wrote:
(1) void LyXParagraph::String(string s)
that writes the paragraph into the string s.
The alternative is
(2) string LyXParagraph::String()
that returns a string from the paragraph.
I'll get this in before you folks head off to your FUND'EM or what ever
you are calling it this year. I'm much to envious to remember.
I would like to be able to define minipage setups in a style file so
that I could get to it the same way I get to Chapter etc. i.e., I want
to say that I want
On Sun, Apr 30, 2000 at 01:15:12AM +0300, Dekel Tsur wrote:
> Yes, but I think that the style I use is quite clear.
> To refresh your memory, I've created a procedure
> (1) void LyXParagraph::String(string & s)
> that writes the paragraph into the string s.
>
> The alternative is
> (2) string
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| > The alternative is
| > (2) string LyXParagraph::String()
| > that returns a string from the paragraph.
| >
| > Do you really think that (2) is clearer/better than (1) ?
| > Should I stay with (1) ?
|
| If the method produces a new
Jules Bean <[EMAIL PROTECTED]> writes:
| (2) says what it means. If efficiency is bothering you, you can save a
| copy by making th procedure return a string&.
No you can't unless you have a static string in the method, or
returning a temporary which is invalid.
Lgb
On Sun, Apr 30, 2000 at 03:27:28AM -0300, Garst R. Reese wrote:
>
> I also noticed that if I set Section Number Depth to -1, clicking on an
> entry in the TOC takes me to the top of the document instead of the
> desired place.
I've rewritten the TOC code, and fixed this bug as a side effect :)
Dekel Tsur wrote:
>
> On Sun, Apr 30, 2000 at 03:27:28AM -0300, Garst R. Reese wrote:
> >
> > I also noticed that if I set Section Number Depth to -1, clicking on an
> > entry in the TOC takes me to the top of the document instead of the
> > desired place.
>
> I've rewritten the TOC code, and
On Sun, Apr 30, 2000 at 12:26:43AM +0200, Asger K. Alstrup Nielsen wrote:
> > (1) void LyXParagraph::String(string & s)
> > that writes the paragraph into the string s.
> >
> > The alternative is
> > (2) string LyXParagraph::String()
> > that returns a string from the paragraph.
> >
> This is
Dekel Tsur wrote:
>
> On Sun, Apr 30, 2000 at 12:26:43AM +0200, Asger K. Alstrup Nielsen wrote:
> > > (1) void LyXParagraph::String(string & s)
> > > that writes the paragraph into the string s.
> > >
> > > The alternative is
> > > (2) string LyXParagraph::String()
> > > that returns a string
I do know that the difference will not be noticeable by the user, but I think
that returning complex objects from functions should be avoided.
In general, it's more important for the code to be clear than for the
code to be fast. This rule should only be lifted if profiling shows
that there
On Sat, Apr 29, 2000 at 04:48:58PM +0200, Asger K. Alstrup Nielsen wrote:
I do know that the difference will not be noticeable by the user, but I think
that returning complex objects from functions should be avoided.
In general, it's more important for the code to be clear than for the
Yes, but I think that the style I use is quite clear.
To refresh your memory, I've created a procedure
(1) void LyXParagraph::String(string s)
that writes the paragraph into the string s.
The alternative is
(2) string LyXParagraph::String()
that returns a string from the paragraph.
> I do know that the difference will not be noticeable by the user, but I think
> that returning complex objects from functions should be avoided.
In general, it's more important for the code to be clear than for the
code to be fast. This rule should only be lifted if profiling shows
that there
On Sat, Apr 29, 2000 at 04:48:58PM +0200, Asger K. Alstrup Nielsen wrote:
> > I do know that the difference will not be noticeable by the user, but I think
> > that returning complex objects from functions should be avoided.
>
> In general, it's more important for the code to be clear than for
> Yes, but I think that the style I use is quite clear.
> To refresh your memory, I've created a procedure
> (1) void LyXParagraph::String(string & s)
> that writes the paragraph into the string s.
>
> The alternative is
> (2) string LyXParagraph::String()
> that returns a string from the
On 28-Apr-2000 Allan Rae wrote:
I can pick them up on my through if JMarc is too slack to come to FILM.
(Or should that be FILM-2 since we had the original FILM years ago)
Well I thought Jean-Marc could drop them by so we will see him at the
meeting too #:O)
Jürgen, where did you dream
sounds awkward and with inappropriate terms. Sorry :-(
You are probably saying I must be crazy to ask for all this, because It
involves to much work, right?
Well, ... I agree and unfortunately I will not be able to contribute at
the moment, not before I finish my PhD.
It is just a wish list.
Best
On 28-Apr-2000 Jean-Marc Lasgouttes wrote:
Juergen Well I thought Jean-Marc could drop them by so we will see
Juergen him at the meeting too #:O)
Ha! And you thought I would fall in that trap?
Well I tried at least :)
Jürgen
"Miguel" == Miguel Velhote Correia [EMAIL PROTECTED] writes:
Miguel 1) to be able to select LaTeX as the native fileformat for
Miguel LyX: I know this has been postponed possibly forever, but I am
Miguel not saying to entirely replace the LyX file format, just to be
Miguel able to switch in
On Thu, Apr 27, 2000 at 10:59:08PM +0200, Asger K. Alstrup Nielsen wrote:
Instead of having a million view_x_command and x_to_y_command in lyxrc, it
may be better to write a general converting/viewing code:
For example, in lyxrc you put lines like
\converter_command dvi ps "dvips"
Dekel Tsur [EMAIL PROTECTED] writes:
| 1. Editing of label insets.
We had that, Alejandro took it out. Shold be easy to put in again.
| 2. Better citation popup (I know that it is possible to use external
| bibliography program, but I do want LyX to have something better than just a
| list of
On Fri, Apr 28, 2000 at 04:22:45PM +0200, Lars Gullik Bjnnes wrote:
Dekel Tsur [EMAIL PROTECTED] writes:
| 1. Editing of label insets.
We had that, Alejandro took it out. Shold be easy to put in again.
| 3. A menu with the table of contents.
Hmm, that was a new idea. I think I like
On 28-Apr-2000 Allan Rae wrote:
>
> I can pick them up on my through if JMarc is too slack to come to FILM.
> (Or should that be FILM-2 since we had the original FILM years ago)
>
Well I thought Jean-Marc could drop them by so we will see him at the
meeting too #:O)
> Jürgen, where did you
sounds awkward and with inappropriate terms. Sorry :-(
You are probably saying I must be crazy to ask for all this, because It
involves to much work, right?
Well, ... I agree and unfortunately I will not be able to contribute at
the moment, not before I finish my PhD.
It is just a wish list.
Best
On 28-Apr-2000 Jean-Marc Lasgouttes wrote:
>
> Juergen> Well I thought Jean-Marc could drop them by so we will see
> Juergen> him at the meeting too #:O)
>
> Ha! And you thought I would fall in that trap?
>
Well I tried at least :)
Jürgen
> "Miguel" == Miguel Velhote Correia <[EMAIL PROTECTED]> writes:
Miguel> 1) to be able to select LaTeX as the native fileformat for
Miguel> LyX: I know this has been postponed possibly forever, but I am
Miguel> not saying to entirely replace the LyX file format, just to be
Miguel> able to
On Thu, Apr 27, 2000 at 10:59:08PM +0200, Asger K. Alstrup Nielsen wrote:
> > Instead of having a million view_x_command and x_to_y_command in lyxrc, it
> > may be better to write a general converting/viewing code:
> > For example, in lyxrc you put lines like
> > \converter_command dvi ps "dvips"
Dekel Tsur <[EMAIL PROTECTED]> writes:
| 1. Editing of label insets.
We had that, Alejandro took it out. Shold be easy to put in again.
| 2. Better citation popup (I know that it is possible to use external
| bibliography program, but I do want LyX to have something better than just a
| list
On Fri, Apr 28, 2000 at 04:22:45PM +0200, Lars Gullik Bjnnes wrote:
> Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> | 1. Editing of label insets.
>
> We had that, Alejandro took it out. Shold be easy to put in again.
>
>
> | 3. A menu with the table of contents.
>
> Hmm, that was a new idea. I
"Ulrich" == Ulrich Günther [EMAIL PROTECTED] writes:
Ulrich I am currently using lyx intensively to write a number of
Ulrich large documents. I almost feal I owe you developers at least a
Ulrich bottle of fine wine. Let we know when you hold a meeting in
Ulrich Germany.
Or you can just send
On 27-Apr-2000 Jean-Marc Lasgouttes wrote:
"Ulrich" == Ulrich Günther [EMAIL PROTECTED] writes:
Ulrich I am currently using lyx intensively to write a number of
Ulrich large documents. I almost feal I owe you developers at least a
Ulrich bottle of fine wine. Let we know when you hold a
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| Ulrich 4. What about adding pdf output (ps2pdf or pdftex)?
|
| There is some preliminary support for pdflatex. Have a look in
| lyxrc.
_very_ preliminary. You are able to set the lyxrc variables, but lyx
will not use them for anything.
Juergen Vigna [EMAIL PROTECTED] writes:
| Well I hope the use is to bring them to the FODEM :)
FODEM? What kind of an acronym is that?
Lgb
1 - 100 of 118 matches
Mail list logo
