Re: lyx, natbib and alternate \cite commands
Angus Leeming [EMAIL PROTECTED] writes: | Yes, a little. I have preliminary natbib support working in my tree. I'd just | like to sort out how LyX stores options to LaTeX commands before releasing | this to the general public. | | Natbib can have up to two options in a \cite field; comments before and after | the citation. LyX can currently deal only with one. To accomodate two is an | ugly and extremely fragile hack. | | Hmmm. Thinking. I COULD ignore the extra options for the time being and just | release a simple patch that gives users the ability to input different \cite | commands. It wouldn't break future compatibility. Are people interested? | | What do people on the devel list think? Can I backport this to 1.1.6 so it | goes in a fix1 release? Let's see how it works in 1.2.0cvs first. Lgb
Re: Longtable function within floats
Jrg Bttcher [EMAIL PROTECTED] writes: | Hi Lars! | It would be nice, if it would be possible to use longtables within floats. AFAIK floats are not supposed to span pages, so this would make little sense. Other know better perhaps. Lgb
Re: lyx, natbib and alternate \cite commands
"Angus" == Angus Leeming [EMAIL PROTECTED] writes: Angus Hmmm. Thinking. I COULD ignore the extra options for the time Angus being and just release a simple patch that gives users the Angus ability to input different \cite commands. It wouldn't break Angus future compatibility. Are people interested? Angus What do people on the devel list think? Can I backport this to Angus 1.1.6 so it goes in a fix1 release? It depends on how simple the patch is. I do not want big code reorganization in fix series, only things that are obviously right (I mean, which cannot possibly break any currently working feature). JMarc
Re: lyx, natbib and alternate \cite commands
Yes, a little. I have preliminary natbib support working in my tree. I'd just like to sort out how LyX stores options to LaTeX commands before releasing this to the general public. Natbib can have up to two options in a \cite field; comments before and after the citation. LyX can currently deal only with one. To accomodate two is an ugly and extremely fragile hack. Hmmm. Thinking. I COULD ignore the extra options for the time being and just release a simple patch that gives users the ability to input different \cite commands. It wouldn't break future compatibility. Are people interested? What do people on the devel list think? Can I backport this to 1.1.6 so it goes in a fix1 release? Angus On Thursday 18 January 2001 03:27, Joshua Rigler wrote: I hate to submit this to the developers list, 'cuz it's not really a bug, so I'll just pass it on to the "lyx-users" list instead, and hope for some response... I submit this message with full knowledge that this has been discussed extensively in the past. I'm just curious why, with such a major change to the citation dialog in LyX 1.1.6, nothing was added to take advantage of natbib? It seems a simple box to enter an alternate \cite command would be an easy first step. Resetting this globally via \renewcommand is easy enough, but I often want different styles of citations within the same paper. The last message I saw discussing this was in the summer of 2000, by Angus Leeming. Has there been any progress since? -EJR
New feature: Bookmarks in LyX?
Hello, I am using LyX 1.1.6 now, really great program. However, I am missing a support for bookmarks in LyX, that is a possibility to set a bookmark (mark a specific place in a document) and to go to a previously set bookmark (return to the marked place in the document later). I know there are many possibilities how one can move around a LyX document (jump to sections, references, etc.), but sometimes they just does not work so well (= fast) for me like true bookmark would do. Would it be possible to implement bookmarks (at least one), please? Thanks a lot! Pavel Cizek
Re: New feature: Bookmarks in LyX?
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | "Pavel" == Pavel Cizek [EMAIL PROTECTED] writes: | | Pavel Hello, I am using LyX 1.1.6 now, really great program. | | Pavel However, I am missing a support for bookmarks in LyX, that is a | Pavel possibility to set a bookmark (mark a specific place in a | Pavel document) and to go to a previously set bookmark (return to the | Pavel marked place in the document later). I know there are many | Pavel possibilities how one can move around a LyX document (jump to | Pavel sections, references, etc.), but sometimes they just does not | Pavel work so well (= fast) for me like true bookmark would do. | | What about using labels for that? Nah.. then you clutter the document. Bookmarks are not really part of the document (even if we store them in the lyx file.) Lgb
Re: New feature: Bookmarks in LyX?
On Thu, Jan 18, 2001 at 11:49:18AM +0100, Pavel Cizek wrote: I am using LyX 1.1.6 now, really great program. However, I am missing a support for bookmarks in LyX, that is a possibility to set a bookmark (mark a specific place in a document) and to go to a previously set bookmark (return to the marked place in the document later). I know there are many possibilities how one can move around a LyX document (jump to sections, references, etc.), but sometimes they just does not work so well (= fast) for me like true bookmark would do. Would it be possible to implement bookmarks (at least one), please? You can use Notes for this (you can bind, for example, Ctrl+j to note-next).
Re: New feature: Bookmarks in LyX?
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Nah.. then you clutter the document. Bookmarks are not really Lars part of the document (even if we store them in the lyx file.) Then we could have transient label insets, which are not saved in the lyx file and not ouput to latex/docbook, but appear (maybe separately) in the reference list. The idea is that the infrastructure for bookmarks is already here. JMarc
Re: New feature: Bookmarks in LyX?
On Thu, Jan 18, 2001 at 12:36:43PM +0100, Jean-Marc Lasgouttes wrote: "Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Nah.. then you clutter the document. Bookmarks are not really Lars part of the document (even if we store them in the lyx file.) Then we could have transient label insets, which are not saved in the lyx file and not ouput to latex/docbook, but appear (maybe separately) in the reference list. The idea is that the infrastructure for bookmarks is already here. We can also add a goto Note dialog (or a general goto inset dialog).
Re: New feature: Bookmarks in LyX?
Jean-Marc Lasgouttes wrote: "Pavel" == Pavel Cizek [EMAIL PROTECTED] writes: Pavel However, I am missing a support for bookmarks in LyX, that is a Pavel possibility to set a bookmark (mark a specific place in a Pavel document) and to go to a previously set bookmark (return to the Pavel marked place in the document later). I know there are many Pavel possibilities how one can move around a LyX document (jump to Pavel sections, references, etc.), but sometimes they just does not Pavel work so well (= fast) for me like true bookmark would do. What about using labels for that? My idea was to have a simple tool to move around documents, not a complicated and slow-to-use bookmark system ala MS Word. That is, for example: I am writing some proof and I would like to check or modify something written in other part of the text (e.g., assumption section). With bookmarks available, press a keyboard shortcut for setting a bookmark; then move around, make changes, whatever...; press a keyboard shortcut to return to the previously set bookmark. Why a special solution, when labels and references exist? - bookmarks are meant just to speed up editing - it is enough to have one bookmark (or three?); thus, it is not necessary to bother user with a dialog to set the name of a bookmark and another one to choose a bookmark to go to -- it is fast - bookmarks does not place any object in the text, there is nothing to remove, when you no longer need a bookmark - bookmarks does not have to be stored (in the document file), they are just temporary within one editing session Of course, I do not know how LyX handles documents internally, so I have no idea whether it is complicated to implement bookmarks or not. Therefore, if there are more people who thinks that bookmarks might be useful and it is not too complicated, please, implement them. Otherwise, just forget it or put it somewhere on TO DO list with a low priority. Would it be possible to implement bookmarks (at least one), please? You can use Notes for this (you can bind, for example, Ctrl+j to note-next). Unfortunately, this does not work very well for me as I use Notes quite often in my documents. Best regards, Pavel Cizek
Re: lyx, natbib and alternate \cite commands
Let's see how it works in 1.2.0cvs first. Fair point. Here is the patch. Visible changes: * Adds a "Use Natbib" check button to the Document dialog (tab Extra). * When natbib is enabled, the Citation dialog has a choice for the \citeX command. * I threw in the Browse Button in Print Dialog patch, because it's small, has no issues associated and I couldn't be bothered separating it out. Issues: * Toggling the "Use Natbib" button does not update the Citation dialog. The dialog must be closed/opened again (or the Restore button pressed if active). * Toggling "Use Natbib" Off will not change the LaTeX output from \citet, \citep etc to \cite. Ie, the output will be incorrect. You'll have to open/close each Citation inset by hand. * Cannot input comments before the citation when in natbib mode. The InsetCommandParams::options field must be altered to take multiple options before this can occur. Thoughts: make options a vectorstring and access is with void setOption(string, int = 0) string getOption(int = 0) ie, behaviour is identical for most insets, but those that want multiple options can have 'em. No idea about how to output this to the LyX file. Any ideas? Finally: I'm not at all sure that I've done the use_natbib stuff correctly. Basically, I just copied use_amsmath. It all seems to work, but if someone in the know would check this over, I'd be very grateful. Angus patch.diff.bz2
Re: Another book written using LyX
"Mike" == [EMAIL PROTECTED] writes: Mike On Wed, 17 Jan 2001, Alejandro Aguilar Sierra wrote: Did anybody know about this book on postgresql? http://www.postgresql.org/docs/awbook.html IMHO the link should be somewhere in the users site, in a section "Who uses LyX". There should be also some other success stories that have been sent to this list, like Garst's ones. Mike Ahem. It's in the FAQ - Section 1.2 "That's fine, but is it Mike useful?". It's time to get the @#$% FAQ on the web page. Anyone Mike want to make a whizzy thing to update an HTML page automatically Mike when I update the LyX file in CVS? You mean here? http://www.sad.it/~jug/lyx/lyxdoc/FAQ/node2.html#SECTION00022000 I do not know how often it is updated, though. JMarc
Re: fax support, dead keys and i18n (1.1.6)
"Thorsten" == Thorsten Mika [EMAIL PROTECTED] writes: Thorsten i do not use a keymap. i see the acute and the grave, but Thorsten they are strangely enough in the middle of the line Thorsten (vertical) and not above the rest...any other idea? Are things better if you use another screen font (something standard like "-*-times")? JMarc
TUI volunteers
Hi all, now that 1.1.6 is closer to GUII and we have task forces for GNOME and KDE ports, I would like to raise your attention to the fact that we can do a TUI (Text-bases User Interface) and do it perfectly workable and enjoyable... In a world of antialiased fonts and annoying multicolor banners, the console is still one of the best mediums to get the job done: either it's better for our eyes on that laptop. it's workable through telnet and similar from a WIn machine w/o an X server, it must be faster to fire up (eg. a quick correction before printing/expoerting) and does not need X, which is okay but can be too much... Some time ago we talked about the TUI and some people showed interest. I think this is a good time to address the issue once more and see who's interested... I guess our best bet would be some ncurses or slang, although I know there must be other very good console toolkits, so let's talk... Whatever we choose, it's better/faster if it has some C++ wrappers so we can integrate it with the code directly and easily, if not, maybe some wrap up OO lib around the C one could be in order, so we get TUI toolkit independence as well (a kind of three layered system, C toolkit || Wrap up TUI API || LyX kernel) Anyone interested in this 'port'? laters and thanks, david PS- I am not subscribed for this list has too high a traffic profile for my mailer, so if you add me in the reply-to: header it's better, but I can access the list through the archives, so it's not necessary for you to bother... thn --- Get free personalized email at http://www.iname.com
Re: lyx-1.16 on hpux
"Klaus" == Klaus Dittrich [EMAIL PROTECTED] writes: Klaus OS: hpux-10.20 with both aCC an gcc-2.75.2 installed. I tried Klaus to get lyx-1.16 up, here my expieriences .. Klaus In ./src/support/fmt.C --- I had to insert Klaus the declaration of vsnprintf in string fmt(char const * fmtstr Klaus ...) extern int vsnprintf(char *, size_t, const char *, Klaus va_list); to get it compiled. Seems configure doesn't configure Klaus HAVE_SNPRINTF properly. Where is vsnprintf defined in HP-UX headers? I do not understand why the configure test compiles correctly, but not the fmt.C file. JMarc
Creating lyx mailing lists for other national languages?
I am currently looking at creating a lyx-fr mailing list to create a viable french LyX community (the main goal is to help the i18n projects). For the sake of consistency (and of my own laziness :), I'd like to create [EMAIL PROTECTED] Thus my questions are: 1/ Mate, are you willing to set this up? 2/ Should we create other lists for other languages? Are there some already existing lists like that? JMarc
Re: TUI volunteers
"excalibor" == excalibor [EMAIL PROTECTED] writes: excalibor Hi all, now that 1.1.6 is closer to GUII and we have task excalibor forces for GNOME and KDE ports, I would like to raise your excalibor attention to the fact that we can do a TUI (Text-bases User excalibor Interface) and do it perfectly workable and enjoyable... That would be fun, indeed, but I think we still heavily rely on X. excalibor I guess our best bet would be some ncurses or slang, excalibor although I know there must be other very good console excalibor toolkits, so let's talk... Is borland TurboVision good? I only know the pascal version, and it allows for all the usual GUI gizmos. It is a C++ library and is public domain, AFAIK. JMarc
Re: New feature: Bookmarks in LyX?
Pavel Cizek [EMAIL PROTECTED] writes: | Jean-Marc Lasgouttes wrote: | | "Pavel" == Pavel Cizek [EMAIL PROTECTED] writes: | | Pavel However, I am missing a support for bookmarks in LyX, that is a | Pavel possibility to set a bookmark (mark a specific place in a | Pavel document) and to go to a previously set bookmark (return to the | Pavel marked place in the document later). I know there are many | Pavel possibilities how one can move around a LyX document (jump to | Pavel sections, references, etc.), but sometimes they just does not | Pavel work so well (= fast) for me like true bookmark would do. | | What about using labels for that? The note inset should be renamed InsetBookmark, a menu item with the list of bookmarks added and a way to id the bookmarks. So that they can be easily moved/jumped to. That is my option. We should have two kindos of bookmars, the default non-peristent ones, and the persistent one.s the non persistent lives only until you kill the document buffer (close) the persistent one lives in the file. Lgb
Re: lyx, natbib and alternate \cite commands
Angus Leeming [EMAIL PROTECTED] writes: | Let's see how it works in 1.2.0cvs first. | | Fair point. | | Here is the patch. Visible changes: | * Adds a "Use Natbib" check button to the Document dialog (tab Extra). I'd rather hide this from the user (and I really want to get rid of the extra stuff). | * When natbib is enabled, the Citation dialog has a choice for the \citeX | command. Those commands should be renamed no "\citeX" anything should ever be visible to the user. | * I threw in the Browse Button in Print Dialog patch, because it's |small, has no issues associated and I couldn't be bothered |separating it out. Please bother. | Issues: | * Toggling the "Use Natbib" button does not update the Citation dialog. The | dialog must be closed/opened again (or the Restore button pressed if active). | | * Toggling "Use Natbib" Off will not change the LaTeX output from \citet, | \citep etc to \cite. Ie, the output will be incorrect. You'll have to | open/close each Citation inset by hand. So this should not be fixed in the inset, but discovered upon writeout. | * Cannot input comments before the citation when in natbib mode. The | InsetCommandParams::options field must be altered to take multiple options | before this can occur. Thoughts: | | make options a vectorstring and access is with | void setOption(string, int = 0) | string getOption(int = 0) hmm, why the int? use a map instead. Look in Variables.C. | ie, behaviour is identical for most insets, but those that want multiple | options can have 'em. No idea about how to output this to the LyX file. Any | ideas? | | Finally: | | I'm not at all sure that I've done the use_natbib stuff correctly. Basically, | I just copied use_amsmath. It all seems to work, but if someone in the know | would check this over, I'd be very grateful. A branch to do this in would probably be nice. Lgb
Re: Creating lyx mailing lists for other national languages?
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | I am currently looking at creating a lyx-fr mailing list to create a | viable french LyX community (the main goal is to help the i18n | projects). For the sake of consistency (and of my own laziness :), I'd | like to create [EMAIL PROTECTED] Thus my questions are: Or I can host it on baywatch/aussie, but then you don't get lists.lyx.org. Then you could be the list admin yourself. Lgb
Re: TUI volunteers
Unfortunately, the GUII only means that the dialog are not dependent on X directly. The main work area is till X dependent, this is a pretty large task to tackle, there is supposedly the Painter class, but too much of LyX depends on Painter itself and not PainterBase. In short, the time is not ripe yet for a TUI, maybe in a version or two we'll be more prepared for this. -- Baruch Even http://baruch.ev-en.org/ (My Site) http://www.redrival.com/jindor/ (My brothers ADD site) " Learn to laugh ... it's the path to true love! " - The Angel in the movie Michael
Re: Creating lyx mailing lists for other national languages?
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | I Lars am currently looking at creating a lyx-fr mailing list to create Lars a | viable french LyX community (the main goal is to help the Lars i18n | projects). For the sake of consistency (and of my own Lars laziness :), I'd | like to create [EMAIL PROTECTED] Thus my Lars questions are: Lars Or I can host it on baywatch/aussie, but then you don't get Lars lists.lyx.org. Then you could be the list admin yourself. Of course [EMAIL PROTECTED] would be fine too, but I thought it would be better to integrate everything, epsecially if lists like lyx-de or lyx-no get created... JMarc
Re: lyx, natbib and alternate \cite commands
On Thu, Jan 18, 2001 at 10:07:26AM +, Angus Leeming wrote: Yes, a little. I have preliminary natbib support working in my tree. I'd just like to sort out how LyX stores options to LaTeX commands before releasing this to the general public. Natbib can have up to two options in a \cite field; comments before and after the citation. LyX can currently deal only with one. To accomodate two is an ugly and extremely fragile hack. Hmmm. Thinking. I COULD ignore the extra options for the time being and just release a simple patch that gives users the ability to input different \cite commands. It wouldn't break future compatibility. Are people interested? What do people on the devel list think? I think the core folks need to discuss handling optional arguments. Unless they have already. I've mentioned before that not taking optional arguments (in \section, \caption, etc.) is one of a very few things that keep LyX from being fully compatible with RevTeX (American Physical Society's class) and other group's classes. Which is too bad, because these groups would be a great source of new users: professors and grad students who are afraid to use plain LaTeX. Wouldn't it be nice to have a link to lyx.org from aps.org etc.? Natbib is (according to Mike) the other reason for not suggesting LyX to large organizations. If you've got it working except for optargs, then that's another reason to have a discussion about optargs. Now that you've got the NEW_INSETS working, it's possible to add optarg support, right? Apologies for doing all this ranting when I won't be doing any of the coding. :( -Amir
Re: lyx, natbib and alternate \cite commands
Amir Karger [EMAIL PROTECTED] writes: | large organizations. If you've got it working except for optargs, then | that's another reason to have a discussion about optargs. Now that you've | got the NEW_INSETS working, it's possible to add optarg support, | right? NEW_INSETS are not quite there yet, so check it out (pun intended) and help finish the last (I believe) few problems. (I will hopefully have some time this weekend.) Lgb
Re: lyx, natbib and alternate \cite commands
Lars,
can I make one point here. This is preliminary work. Nobody was suggesting
that it would be the best possible way.
Right. Now I've said that, I'll answer your points.
| * Adds a "Use Natbib" check button to the Document dialog (tab Extra).
I'd rather hide this from the user (and I really want to get rid of
the extra stuff).
This means that natbib will always be used. Is this what you want? Why?
Moreover, the \usepackage{natbib} command can take a raft of options. This
should go in the Document dialog somewhere, probably in it's own, dedicated
tab folder.
| * When natbib is enabled, the Citation dialog has a choice for the \citeX
| command.
Those commands should be renamed no "\citeX" anything should ever be
visible to the user.
Whilst I see that I could use two checkboxes to go from \citeX to \citeX* or
from \citeX to \CiteX, natbib supports so many different \citeX commands that
I really can't see how better to do this. Anyway, the principle point
remains. This is preliminary work.
| * Toggling "Use Natbib" Off will not change the LaTeX output from \citet,
| \citep etc to \cite. Ie, the output will be incorrect. You'll have to
| open/close each Citation inset by hand.
So this should not be fixed in the inset, but discovered upon
writeout.
Yes, this is what I've just done. Overload the InsetCite::Latex() method.
However, if we ALWAYS use natbib, then the code isn't needed. So, the "design
argument" should be thrashed out.
| * Cannot input comments before the citation when in natbib mode.
| The InsetCommandParams::options field must be altered to take
| multiple options before this can occur. Thoughts:
|
| make options a vectorstring and access is with
| void setOption(string, int = 0)
| string getOption(int = 0)
hmm, why the int? use a map instead.
Look in Variables.C.
My turn to hmm. Not sure I understand you. A generic latex command can take
multiple options
\cmdname [option1] [option2] [option X] {contents}
why would a map represent this concept more cleanly? Are you talking about
using a map to store the data rather than a vector? But this is an
implementation detail, not an interface one.
| I'm not at all sure that I've done the use_natbib stuff correctly.
| Basically, I just copied use_amsmath. It all seems to work, but if
| someone in the know would check this over, I'd be very grateful.
A branch to do this in would probably be nice.
Ok. Will this work: (and do I have write permission?)
To create a branch of lyx-devel
===
1. create a tag at the current point
cvs tag natbib-TAG lyx-devel
2. create a branch tag on that tag
cvs rtag -b -r natbib-TAG natbib-BRANCH lyx-devel
3. checkout
cvs checkout -r natbib-BRANCH
4. apply my changes to this checked out code
patch -p0 patch_natbib
5. commit the changes
cvs commit
Angus
Re: lyx, natbib and alternate \cite commands
On Thu, Jan 18, 2001 at 03:46:46PM +0100, Lars Gullik Bjønnes wrote: Angus Leeming [EMAIL PROTECTED] writes: | Here is the patch. Visible changes: | * Adds a "Use Natbib" check button to the Document dialog (tab Extra). I'd rather hide this from the user (and I really want to get rid of the extra stuff). But perhaps we do need a citation tab in the Document dialog which will contain the bibilography-style (this should not be stored in the bibtex inset), citation mode (author-year/numerical) and the citation style. I do agree that the decision whether to use natbib should be made by LyX. | I'm not at all sure that I've done the use_natbib stuff correctly. Basically, | I just copied use_amsmath. It all seems to work, but if someone in the know | would check this over, I'd be very grateful. A branch to do this in would probably be nice. I think that there are too few changes here to require a branch.
Re: New feature: Bookmarks in LyX?
On 18 Jan 2001, Lars Gullik Bjnnes wrote: The note inset should be renamed InsetBookmark, a menu item with the list of bookmarks added and a way to id the bookmarks. So that they can be easily moved/jumped to. That is my option. We should have two kindos of bookmars, the default non-peristent ones, and the persistent one.s The persistent ones are already called "labels" and there are already ways to navigate between references (goto and return). Alejandro
Re: New feature: Bookmarks in LyX?
Alejandro Aguilar Sierra [EMAIL PROTECTED] writes: | On 18 Jan 2001, Lars Gullik Bjnnes wrote: | | The note inset should be renamed InsetBookmark, a menu item with the | list of bookmarks added and a way to id the bookmarks. So that they | can be easily moved/jumped to. | | That is my option. | | We should have two kindos of bookmars, the default non-peristent ones, | and the persistent one.s | | The persistent ones are already called "labels" and there are already ways | to navigate between references (goto and return). No. The persisten ones are today called "Notes" and there are no way to navigate quickly beween them or to them. Lgb
Re: lyx, natbib and alternate \cite commands
Dekel Tsur [EMAIL PROTECTED] writes: | On Thu, Jan 18, 2001 at 03:46:46PM +0100, Lars Gullik Bjnnes wrote: | Angus Leeming [EMAIL PROTECTED] writes: | | Here is the patch. Visible changes: | | * Adds a "Use Natbib" check button to the Document dialog (tab Extra). | | I'd rather hide this from the user (and I really want to get rid of | the extra stuff). | | But perhaps we do need a citation tab in the Document dialog which will | contain the bibilography-style (this should not be stored in the bibtex | inset), citation mode (author-year/numerical) and the citation style. | I do agree that the decision whether to use natbib should be made by LyX. | | | I'm not at all sure that I've done the use_natbib stuff correctly. Basically, | | I just copied use_amsmath. It all seems to work, but if someone in the know | | would check this over, I'd be very grateful. | | A branch to do this in would probably be nice. | | I think that there are too few changes here to require a branch. A branch to "finish" the support for natbib, not to add this preliminary patch. Lgb
Re: New feature: Bookmarks in LyX?
a long, long time ago... We were having this self-same discussion. I wrote a new InsetNote. It did nothing but replace InsetInfo with GUI-I and NEW_INSET code. Shall I resubmit it again now that NEW_INSETs are go? It'll provide the starting point for some real work on this. I seem to remember that at the time we defined THREE possible notes. It's all in the archives... Also note that Jean-Marc and Dekel have both proposed a general gotoInset dialog analogous to the FindReplace dialog for text. Angus On Thursday 18 January 2001 15:47, Lars Gullik Bjnnes wrote: Alejandro Aguilar Sierra [EMAIL PROTECTED] writes: | On 18 Jan 2001, Lars Gullik Bjnnes wrote: | | The note inset should be renamed InsetBookmark, a menu item with the | list of bookmarks added and a way to id the bookmarks. So that they | can be easily moved/jumped to. | | That is my option. | | We should have two kindos of bookmars, the default non-peristent ones, | and the persistent one.s | | The persistent ones are already called "labels" and there are already ways | to navigate between references (goto and return). No. The persisten ones are today called "Notes" and there are no way to navigate quickly beween them or to them. Lgb
Re: lyx, natbib and alternate \cite commands
Angus Leeming [EMAIL PROTECTED] writes:
| Lars,
| can I make one point here. This is preliminary work. Nobody was suggesting
| that it would be the best possible way.
I know that.
| Right. Now I've said that, I'll answer your points.
|
| | * Adds a "Use Natbib" check button to the Document dialog (tab Extra).
| I'd rather hide this from the user (and I really want to get rid of
| the extra stuff).
|
| This means that natbib will always be used. Is this what you want?
| Why?
No, LyX knows if natbib is available. and use it if present, if
features is used that we can't do with out we give a warning and use a
working non-optimal solution instead.
| Moreover, the \usepackage{natbib} command can take a raft of options. This
| should go in the Document dialog somewhere, probably in it's own, dedicated
| tab folder.
The options:
- text before [abc][]
- text after [abc]
(- text before and after [abc][abc])
- full name
- with parantesis
- mode author-year/numerical
These are the options in 4.2 in the natbib doc.
The options in 4.3. should also be supported, but not absolutely for
the first implementation.
All of this should be possible to set in .layout and in
Document-Citation, however individual style on each InsetCitation
should also be possible. Pluss separate config of the Bibliography
style (the list of references.)
| | * When natbib is enabled, the Citation dialog has a choice for the \citeX
| | command.
|
| Those commands should be renamed no "\citeX" anything should ever be
| visible to the user.
|
| Whilst I see that I could use two checkboxes to go from \citeX to \citeX* or
| from \citeX to \CiteX, natbib supports so many different \citeX commands that
| I really can't see how better to do this. Anyway, the principle point
| remains. This is preliminary work.
And don't try to support everything at once, select the most needed
subset.
| hmm, why the int? use a map instead.
| Look in Variables.C.
|
| My turn to hmm. Not sure I understand you. A generic latex command can take
| multiple options
|
| \cmdname [option1] [option2] [option X] {contents}
|
| why would a map represent this concept more cleanly? Are you talking about
| using a map to store the data rather than a vector? But this is an
| implementation detail, not an interface one.
We are not talking generig latex commands here... And I do not reallt
se how citation really plays in (but we solve it by having insets in
insets.)
| Ok. Will this work: (and do I have write permission?)
No, not yet, You did not take part in the "what dir do yo uneed write
permissions to" discussion.
| To create a branch of lyx-devel
You really should read the doc I posted a while ago.
| ===
| 1. create a tag at the current point
| cvs tag natbib-TAG lyx-devel
I belive it was TAG_CREATE_natbib
| 2. create a branch tag on that tag
| cvs rtag -b -r natbib-TAG natbib-BRANCH lyx-devel
BRANCH_natbib
| 3. checkout
| cvs checkout -r natbib-BRANCH
or from inside your already checked out dir:
cvs update -r BRANCH_natbib
| 4. apply my changes to this checked out code
| patch -p0 patch_natbib
if as above:
cvs update
cvs commit
Lgb
Re: New feature: Bookmarks in LyX?
Angus Leeming [EMAIL PROTECTED] writes: | We were having this self-same discussion. I wrote a new InsetNote. It did | nothing but replace InsetInfo with GUI-I and NEW_INSET code. Shall I resubmit | it again now that NEW_INSETs are go? Yes, but against the NEW_INSET branch. | It'll provide the starting point for | some real work on this. I seem to remember that at the time we defined THREE | possible notes. It's all in the archives... Care to spare me the digging? | Also note that Jean-Marc and Dekel have both proposed a general gotoInset | dialog analogous to the FindReplace dialog for text. I am not sure if this will cut it. We want to ge able to move quickly to InsetBookmark named: "1" (and no dialog should be needed) Lgb
Re: Two ideas
On Tue, Jan 16, 2001 at 04:33:51PM -0600, Brett Jones wrote: When using nested bullets, etc., it seems to me that when increasing the depth of a bullet, all bullets nested beneath that bullet should also be bumped down a level. Of course, bumping up against the maximum depth would be a special case. Also, just my opinion, but I would think it more intuitive to stay at the current depth when hitting return on a bullet, rather than explicitly having to hit M-Return. Jumping back up a level should have to be explicit imho. I agree with the above. However, is there a future plan to replace the current paragraph layout mechanism by insets ? (namely, we will have enumerate inset, section inset etc).
Re: Displaystyle
On Tue, Jan 16, 2001 at 02:21:31PM +0100, Hartmut S. Leipner wrote:
I cannot change the size of parts of an equation by setting displaystyle. At
a first glance it seems to work. However after saving and reopening the file
all special size settings are gone. This does not work neither with the input
in the minibuffer (math-size displaystyle) nor by direct input in tex code
(\displaystyle).
I think that the mathed sometimes get confused with font changing commands,
namely, this is a bug.
One way to cope with this bug is to put
\newcommand{\dstyle}[1]{\displaystyle{#1}}
in the preamble, and use the \dstyle command in the mathed.
Re: lyx, natbib and alternate \cite commands
No, not yet, You did not take part in the "what dir do yo uneed write permissions to" discussion. Perhaps this was whilst my computer was belly side -up? You really should read the doc I posted a while ago. If I could find it, I would. Can you remember it's title or such like? | 1. create a tag at the current point | cvs tag natbib-TAG lyx-devel I belive it was TAG_CREATE_natbib I'm glad I got this mail before proceeding further. Ok, before I cook my goose and piss everybody off. I have just typed from my own top directory of lyx-devel (plase note that this is EXACTLY what I typed): cvs tag natbib-TAG to get [EMAIL PROTECTED]'s password: T .cvsignore T ABOUT-NLS T ANNOUNCE etc and cvs rtag -R -b -r natbib-TAG natbib-BRANCH lyx-devel to get [EMAIL PROTECTED]'s password: cvs server: Tagging lyx-devel cvs server: Tagging lyx-devel/boost etc. So it appears that I do have write access? I was about to type cvs update cvs commit when I recieved your mail, Lars. However, if I've done this incorrectly, can you tell me how to undo it? I'll wait to hear from you before doing anything further. Angus | 2. create a branch tag on that tag | cvs rtag -b -r natbib-TAG natbib-BRANCH lyx-devel BRANCH_natbib | 3. checkout | cvs checkout -r natbib-BRANCH or from inside your already checked out dir: cvs update -r BRANCH_natbib | 4. apply my changes to this checked out code | patch -p0 patch_natbib if as above: cvs update cvs commit Lgb
Re: Two ideas
Dekel Tsur [EMAIL PROTECTED] writes: | I agree with the above. | However, is there a future plan to replace the current paragraph layout | mechanism by insets ? (namely, we will have enumerate inset, section inset | etc). Yes, at least I want to do that. Especially the lists. They are really cluttering up LyXText Lgb
Re: Two ideas
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes: Dekel I agree with the above. However, is there a future plan to Dekel replace the current paragraph layout mechanism by insets ? Dekel (namely, we will have enumerate inset, section inset etc). I'd like to avoid that. The idea I have been advocating is to keep the main text as a paragraph, but use insets as needed (the \item of a list, the optional argument of section...). Juergen said at the time he has ideas on how to do that. JMarc
Re: TUI volunteers
Hi all, Jean-Marc wrote: That would be fun, indeed, but I think we still heavily rely on X. Nod... but we can start preparing for the day we're free :) After all, the GNOME/KDE task forces are already working on it... excalibor I guess our best bet would be some ncurses or slang, excalibor although I know there must be other very good console excalibor toolkits, so let's talk... Is borland TurboVision good? I only know the pascal version, and it allows for all the usual GUI gizmos. It is a C++ library and is public domain, AFAIK. It's GPL, nod... I've downloaded version 0.6 to evaluate it... Also found Terminality (http://members.optushome.com.au/darkmoon7/term.html) it uses ncurses but looks pretty stable and usable... some of the screens are cool (and the API is similar to the Borland one) Maybe the best would be to wrap the TUI capability in a thin layer so it can be built either with ncurses, s-lang, or any of the other useful packages... It may be not too difficult (obviously, requiring one of the non-usual libraries will make it harder for people to use...) Someone interested in having a look at how this could possibly be made? I haven't checked the GUII code... (actually haven't downloaded 1.1.6, it's not in the ftp server (?)) best regards, david --- Get free personalized email at http://www.iname.com
Re: New feature: Bookmarks in LyX?
On Thursday 18 January 2001 16:25, Lars Gullik Bjønnes wrote: Angus Leeming [EMAIL PROTECTED] writes: | We were having this self-same discussion. I wrote a new InsetNote. It did | nothing but replace InsetInfo with GUI-I and NEW_INSET code. Shall I resubmit | it again now that NEW_INSETs are go? Yes, but against the NEW_INSET branch. Oh, Lordy. I need to read that article! | It'll provide the starting point for | some real work on this. I seem to remember that at the time we defined THREE | possible notes. It's all in the archives... Care to spare me the digging? http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg14517.html So, care to reciprocate the favour and tell me wherre to find your cvs article? | Also note that Jean-Marc and Dekel have both proposed a general gotoInset | dialog analogous to the FindReplace dialog for text. I am not sure if this will cut it. We want to ge able to move quickly to InsetBookmark named: "1" (and no dialog should be needed) Lgb
Re: lyx, natbib and alternate \cite commands
On 18 Jan 2001, Lars Gullik Bjnnes wrote: Angus Leeming [EMAIL PROTECTED] writes: | Right. Now I've said that, I'll answer your points. | | | * Adds a "Use Natbib" check button to the Document dialog (tab Extra). | I'd rather hide this from the user (and I really want to get rid of | the extra stuff). | | This means that natbib will always be used. Is this what you want? | Why? No, LyX knows if natbib is available. and use it if present, if features is used that we can't do with out we give a warning and use a working non-optimal solution instead. Lgb LyX knows if natbib is available at the current installation. But suppose I want to export-to-LaTeX and share the file with someone? There must be some way to ignore the idiosyncrasies of a particular installation. Lior.
Re: New feature: Bookmarks in LyX?
On Thu, 18 Jan 2001, Pavel Cizek wrote: [snip] My idea was to have a simple tool to move around documents, not a complicated and slow-to-use bookmark system ala MS Word. That is, for example: I am writing some proof and I would like to check or modify something written in other part of the text (e.g., assumption section). With bookmarks available, press a keyboard shortcut for setting a bookmark; then move around, make changes, whatever...; press a keyboard shortcut to return to the previously set bookmark. [snip] Best regards, Pavel Cizek It seems you want to be able to set a single bookmark, and then get there with a keypress. This bookmark can be easily moved (just set it somewhere else). The discussion seems to focus on adding/adapting support for multiple bookmarks you can cycle through with a keypress, so you have to explicitely remove them when you don't need them (or by closing the file). Which of the two is preferable ? Lior.
Re: lyx, natbib and alternate \cite commands
On Thu, Jan 18, 2001 at 03:34:27PM +, Angus Leeming wrote: | * When natbib is enabled, the Citation dialog has a choice for the \citeX | command. Those commands should be renamed no "\citeX" anything should ever be visible to the user. Whilst I see that I could use two checkboxes to go from \citeX to \citeX* or from \citeX to \CiteX, natbib supports so many different \citeX commands that I really can't see how better to do this. Anyway, the principle point remains. This is preliminary work. Word's Date popup gives you a bunch of possible options. You could do the same in the cite popup: Format: (Jones et al. 1990) Jones et al. (1990) Jones, Baker, and Williams (1990) Jones et al. 1990 Jones et al. 1990 Of course, if the person had selected to use numerical references, you would want this to show up as Jones et al. [2] [2] etc. Of course, this depends on whether the user selected numbers or authoryear for their citations. I don't know whether you'd want to have the default outlined or have it greyed out with a checkbox for "special citation" or some such. -Amir
Re: lyx, natbib and alternate \cite commands
Angus Leeming [EMAIL PROTECTED] writes: | No, not yet, You did not take part in the "what dir do yo uneed write | permissions to" discussion. | | Perhaps this was whilst my computer was belly side -up? Or perhaps because you were not on that mailinglist... | You really should read the doc I posted a while ago. | If I could find it, I would. Can you remember it's title or such like? "Better use of CVS" or something | | 1. create a tag at the current point | | cvs tag natbib-TAG lyx-devel | | I belive it was TAG_CREATE_natbib | | I'm glad I got this mail before proceeding further. | Ok, before I cook my goose and piss everybody off. | | I have just typed from my own top directory of lyx-devel (plase note that | this is EXACTLY what I typed): | cvs tag natbib-TAG | to get | [EMAIL PROTECTED]'s password: | T .cvsignore | T ABOUT-NLS | T ANNOUNCE | etc | | and | cvs rtag -R -b -r natbib-TAG natbib-BRANCH lyx-devel | to get | [EMAIL PROTECTED]'s password: | cvs server: Tagging lyx-devel | cvs server: Tagging lyx-devel/boost | etc. | | So it appears that I do have write access? | I was about to type | cvs update | cvs commit | when I recieved your mail, Lars. You were to quick with this. You are no followin ghte naming standard for tags. | However, if I've done this incorrectly, can you tell me how to undo it? I'll | wait to hear from you before doing anything further. Just remove the tags you added with : cvs rtag -d tag lyx-devel (the branch first then the other) Lgb
Re: lyx, natbib and alternate \cite commands
Angus Leeming [EMAIL PROTECTED] writes: | cvs rtag -R -b -r natbib-TAG natbib-BRANCH lyx-devel this "-R" is not needed that is default. | So it appears that I do have write access? No, but you don't need that you create tags and such. | I was about to type | cvs update | cvs commit Good. This would have been incorrect. after you create the branch you _must_ update-r branch , if not you will still be on the HEAD (I am pretty sure about this, check CVS/Entries) Lgb
Re: Another book written using LyX
On 18 Jan 2001, Jean-Marc Lasgouttes wrote: "Mike" == [EMAIL PROTECTED] writes: Mike Ahem. It's in the FAQ - Section 1.2 "That's fine, but is it Mike useful?". It's time to get the @#$% FAQ on the web page. Anyone Mike want to make a whizzy thing to update an HTML page automatically Mike when I update the LyX file in CVS? You mean here? http://www.sad.it/~jug/lyx/lyxdoc/FAQ/node2.html#SECTION00022000 Yes, I know that exists (and I'm glad it does), but there should be a pointer on the www.lyx.org front page that points to an autogenerated FAQ.html derived from the lyxdoc CVS. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: lyx, natbib and alternate \cite commands
Lior Silberman [EMAIL PROTECTED] writes: | No, LyX knows if natbib is available. and use it if present, if | features is used that we can't do with out we give a warning and use a | working non-optimal solution instead. | | Lgb | | | LyX knows if natbib is available at the current installation. But suppose | I want to export-to-LaTeX and share the file with someone? There must be | some way to ignore the idiosyncrasies of a particular installation. Yes, then we use the non-optimal solution which will usually be a regular "\cite". Lgb
Lyx 1.1.6 - menu entries
Hi, I had used lyx 1.1.5-fix2 before (from the RPM), then upgraded to 1.1.6 (src). The problem I have now is that when I open a file (or create a new one), the extra menu entries (TOC, Math, Help etc.) are not "unlocked". Also, "Edit" only contains a few basic entries (cut/copy/paste I think). I had to downgrade again in order to use Lyx. I use gcc-2.96-54 from RedHat 7.0 (I know everybody loves this inofficial compiler release). -- Regards, Cyrille Artho - http://artho.com/ - Tel. +1 - 512 - 532 52 65 Thieves respect property; they merely wish the property to become their property that they may more perfectly respect it. -- G.K. Chesterton, "The Man Who Was Thursday"
Re: DVI view update problem
Dekel Tsur [EMAIL PROTECTED] writes: | On Tue, Jan 16, 2001 at 09:09:18AM +, Adrian Ball wrote: |I am having real trouble with previewing the document I am working on. |Everything works fine, but running a preview consistently shows me a previous |version. The only way to fix it easily is to close and reopen the document, |then preview it. | | This might be a bug. | Please run LyX with the '-dbg depend' flag, open a file, do view-dvi, | make a change in the file, and do view-dvi again. | Now, send to lyx-devel all the debug messages from LyX. | | I have done exactly as requested - Second DVI view the same as the first, | debug output attached in gz format. | | I think that the problem is that you have a file called | "/home/adrian/suneds/docs//eds_logo.eps Graphic file (type eps)" | and LaTeX/LyX don't like spaces in filenames. | | The exact problem here is in DepTable::read which assumes there are no spaces | in the filenames. Are you telling me that latex grok the filenames ok? If so I will change the DepTable code. (will be harder to find the filename...) Lgb
Re: lyx, natbib and alternate \cite commands
On Thu, Jan 18, 2001 at 04:39:19PM +, Angus Leeming wrote: If I could find it, I would. Can you remember it's title or such like? I am not Lars, but here it is: Date: 31 Oct 2000 05:38:12 +0100 From: [EMAIL PROTECTED] (Lars Gullik Bjnnes) Subject: Better use of CVS This should help... -- Jos
list of float
AFAICS lists of floats have never been supported. Also the current support are only workable for TOC and noto for any of the float lists since the number of these will by dynamic. (the user can create its own kind of floats.) Who created this lists support? Dekel? Other than that the float support in NEW_INSETS are pretty good for tables and figures. algorighmt still need some small bits. I'd also like to replace the current "caption" paragraph style with a InsetCaption. Lgb
Re: Goto inset patch
On Mon, Jan 15, 2001 at 05:56:50PM +0100, Jean-Marc Lasgouttes wrote: Dekel Should I also replace error-next, error-note and reference-next Dekel lyxfuncs by a general inset-next lyxfunc ? Something like "inset-next error"? I'm not sure it will be more general, just different. Are there any objections to this change ? (it will break user defined bindings but that is not a big problem).
Re: LyX 1.1.6 and DocBook
On Mon, Jan 15, 2001 at 05:10:28PM +, Jose Abilio Oliveira Matos wrote: Is this clear? The problem now is that nice (the parameter) is always set to true. So we just need to replace 'true' by 'backend_format == format' ? I'm going to rewrite the include code to fix the nested include bug. It will also change the behavior for linuxdoc/docbook: Currently, when temp_dir=true, the included sgml files are written to the directory of the lyx file. I'll change that so they will be written to the temp. directory. For now that is not a problem for linuxdoc/docbook. What do you mean ? If temp_dir = true then all temporary files should be written to the temp. directory, which is currently not the case for the sgml files.
Re: fax support, dead keys and i18n (1.1.6)
hi, Thorsten i do not use a keymap. i see the acute and the grave, but Thorsten they are strangely enough in the middle of the line Thorsten (vertical) and not above the rest...any other idea? Are things better if you use another screen font (something standard like "-*-times")? nope, just checked it with several standard fonts but no difference thorsten Thorsten Mika mailto:[EMAIL PROTECTED] Hamm / GermanyTM5173-RIPE
Re: DVI view update problem
On Thu, Jan 18, 2001 at 06:41:32PM +0100, Lars Gullik Bjønnes wrote: | I think that the problem is that you have a file called | "/home/adrian/suneds/docs//eds_logo.eps Graphic file (type eps)" | and LaTeX/LyX don't like spaces in filenames. | | The exact problem here is in DepTable::read which assumes there are no spaces | in the filenames. Are you telling me that latex grok the filenames ok? I don't know. I was just looking at the debug messages he sent: Found file: /home/adrian/suneds/docs//eds_logo.eps Graphic file (type eps) AbsolutePath file: /home/adrian/suneds/docs//eds_logo.eps Graphic file (type eps) If so I will change the DepTable code. (will be harder to find the filename...)
Re: Lyx-1.1.6 and Included files
Hello,
The bug is in lyx_func.C (patch at the end of this message), where
insetinclude was changed to get the command name as a parameter (rather
than being hard-coded). (lyx_func.C rev. 1.113, insetinclude.C rev 1.37)
Lior.
On Thu, 18 Jan 2001, ben wrote:
Hello,
I've seen the following problem in lyx-1.1.6: when I include a lyx file
into another lyx file, the latex compilation fails because the
translation is:
\Include{the_subfile}
instead of:
\include{the_subfile}
Of course putting \def\Include#1{\include{#1}} in the pramble makes it
work, but it is a temporary fix.
Bye,
BG
Index: lyxfunc.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/lyxfunc.C,v
retrieving revision 1.177
diff -u -r1.177 lyxfunc.C
--- lyxfunc.C 2001/01/15 18:54:29 1.177
+++ lyxfunc.C 2001/01/18 22:39:00
@@ -2751,7 +2751,7 @@
case LFUN_CHILDINSERT:
{
- InsetCommandParams p( "Include", argument );
+ InsetCommandParams p( "include", argument );
Inset * inset = new InsetInclude(p, *owner-buffer());
if (owner-view()-insertInset(inset, "Standard", true))
inset-Edit(owner-view(), 0, 0, 0);
Re: $LANG specific menus not possible in 1.1.6
Could this be the the 'make install' requirement for i18n menus that was discussed a few days ago? Lior. On Thu, 18 Jan 2001, Claus Hentschel wrote: Claus === 1) One problem is that although I have set LANG=de_DE the Claus german menus will not open! BUT: Passing -dbg 32 shows that Claus de_menus.bind will be loaded. So I am working with default Claus english menus but have to use the german shortcuts!?!?! What Claus has been changed in the code that language support does not Claus function as before? Do you use the very latest po files from Pit Sutterlin? The menu code has completely changed, so all the menu translations had to be redone. Also, the german shortcuts of de_menus.bind are now _only_ those which are not in the menus! I am using the po files from the lyx source file (fetched monday, january 15). Are there still other po files available? At the moment the following does happen: - the mo files are located in ...lyx/lib/locale/xx/lyx.mo - gdb shows that lyx uses ...lyx/share/locale as its LOCALEDIR by default (so it can't find the files!) - doing ln -s form lib/locale to share/locale and starting lyx results in a core dump! Why does 'make install' does install the mo files in a directory which is not set by default? There was no ...lyx/lib directory in any version before!?!? Regards Claus P.S.: All old functions but the language specific part are still running under Win32! (It looks great! Good work from all of u!!!) P.P.S: I now want to test the new features like gif image includes. Which utility is necessary for that (and for the others)? Is that written in any document available?
Re: New feature: Bookmarks in LyX?
On 18 Jan 2001, Lars Gullik Bjnnes wrote: | The persistent ones are already called "labels" and there are already ways | to navigate between references (goto and return). No. The persisten ones are today called "Notes" and there are no way to navigate quickly beween them or to them. That's what I mean, we have reference-goto and reference-back for labels already for labels. Alejandro
Re: lyx, natbib and alternate \cite commands
Angus Leeming <[EMAIL PROTECTED]> writes: | Yes, a little. I have preliminary natbib support working in my tree. I'd just | like to sort out how LyX stores options to LaTeX commands before releasing | this to the general public. | | Natbib can have up to two options in a \cite field; comments before and after | the citation. LyX can currently deal only with one. To accomodate two is an | ugly and extremely fragile hack. | | Hmmm. Thinking. I COULD ignore the extra options for the time being and just | release a simple patch that gives users the ability to input different \cite | commands. It wouldn't break future compatibility. Are people interested? | | What do people on the devel list think? Can I backport this to 1.1.6 so it | goes in a fix1 release? Let's see how it works in 1.2.0cvs first. Lgb
Re: Longtable function within floats
Jörg Böttcher <[EMAIL PROTECTED]> writes: | Hi Lars! | It would be nice, if it would be possible to use longtables within floats. AFAIK floats are not supposed to span pages, so this would make little sense. Other know better perhaps. Lgb
Re: lyx, natbib and alternate \cite commands
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Hmmm. Thinking. I COULD ignore the extra options for the time Angus> being and just release a simple patch that gives users the Angus> ability to input different \cite commands. It wouldn't break Angus> future compatibility. Are people interested? Angus> What do people on the devel list think? Can I backport this to Angus> 1.1.6 so it goes in a fix1 release? It depends on how simple the patch is. I do not want big code reorganization in fix series, only things that are obviously right (I mean, which cannot possibly break any currently working feature). JMarc
Re: lyx, natbib and alternate \cite commands
Yes, a little. I have preliminary natbib support working in my tree. I'd just like to sort out how LyX stores options to LaTeX commands before releasing this to the general public. Natbib can have up to two options in a \cite field; comments before and after the citation. LyX can currently deal only with one. To accomodate two is an ugly and extremely fragile hack. Hmmm. Thinking. I COULD ignore the extra options for the time being and just release a simple patch that gives users the ability to input different \cite commands. It wouldn't break future compatibility. Are people interested? What do people on the devel list think? Can I backport this to 1.1.6 so it goes in a fix1 release? Angus On Thursday 18 January 2001 03:27, Joshua Rigler wrote: > I hate to submit this to the developers list, 'cuz it's not really a > bug, so I'll just pass it on to the "lyx-users" list instead, and hope > for some response... > > I submit this message with full knowledge that this has been discussed > extensively in the past. I'm just curious why, with such a major change > to the citation dialog in LyX 1.1.6, nothing was added to take advantage > of natbib? It seems a simple box to enter an alternate \cite command > would be an easy first step. Resetting this globally via \renewcommand > is easy enough, but I often want different styles of citations within > the same paper. > > The last message I saw discussing this was in the summer of 2000, by > Angus Leeming. Has there been any progress since? > > -EJR
New feature: Bookmarks in LyX?
Hello, I am using LyX 1.1.6 now, really great program. However, I am missing a support for bookmarks in LyX, that is a possibility to set a bookmark (mark a specific place in a document) and to go to a previously set bookmark (return to the marked place in the document later). I know there are many possibilities how one can move around a LyX document (jump to sections, references, etc.), but sometimes they just does not work so well (= fast) for me like true bookmark would do. Would it be possible to implement bookmarks (at least one), please? Thanks a lot! Pavel Cizek
Re: New feature: Bookmarks in LyX?
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | > "Pavel" == Pavel Cizek <[EMAIL PROTECTED]> writes: | | Pavel> Hello, I am using LyX 1.1.6 now, really great program. | | Pavel> However, I am missing a support for bookmarks in LyX, that is a | Pavel> possibility to set a bookmark (mark a specific place in a | Pavel> document) and to go to a previously set bookmark (return to the | Pavel> marked place in the document later). I know there are many | Pavel> possibilities how one can move around a LyX document (jump to | Pavel> sections, references, etc.), but sometimes they just does not | Pavel> work so well (= fast) for me like true bookmark would do. | | What about using labels for that? Nah.. then you clutter the document. Bookmarks are not really part of the document (even if we store them in the lyx file.) Lgb
Re: New feature: Bookmarks in LyX?
On Thu, Jan 18, 2001 at 11:49:18AM +0100, Pavel Cizek wrote: > I am using LyX 1.1.6 now, really great program. > > However, I am missing a support for bookmarks in LyX, that is a > possibility to set a bookmark (mark a specific place in a document) and > to go to a previously set bookmark (return to the marked place in the > document later). I know there are many possibilities how one can move > around a LyX document (jump to sections, references, etc.), but > sometimes they just does not work so well (= fast) for me like true > bookmark would do. > > Would it be possible to implement bookmarks (at least one), please? You can use Notes for this (you can bind, for example, Ctrl+j to note-next).
Re: New feature: Bookmarks in LyX?
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> Nah.. then you clutter the document. Bookmarks are not really Lars> part of the document (even if we store them in the lyx file.) Then we could have transient label insets, which are not saved in the lyx file and not ouput to latex/docbook, but appear (maybe separately) in the reference list. The idea is that the infrastructure for bookmarks is already here. JMarc
Re: New feature: Bookmarks in LyX?
On Thu, Jan 18, 2001 at 12:36:43PM +0100, Jean-Marc Lasgouttes wrote: > > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: > > Lars> Nah.. then you clutter the document. Bookmarks are not really > Lars> part of the document (even if we store them in the lyx file.) > > Then we could have transient label insets, which are not saved in the > lyx file and not ouput to latex/docbook, but appear (maybe separately) > in the reference list. The idea is that the infrastructure for > bookmarks is already here. We can also add a goto Note dialog (or a general goto inset dialog).
Re: New feature: Bookmarks in LyX?
Jean-Marc Lasgouttes wrote: > > "Pavel" == Pavel Cizek <[EMAIL PROTECTED]> writes: > > Pavel> However, I am missing a support for bookmarks in LyX, that is a > Pavel> possibility to set a bookmark (mark a specific place in a > Pavel> document) and to go to a previously set bookmark (return to the > Pavel> marked place in the document later). I know there are many > Pavel> possibilities how one can move around a LyX document (jump to > Pavel> sections, references, etc.), but sometimes they just does not > Pavel> work so well (= fast) for me like true bookmark would do. > > What about using labels for that? My idea was to have a simple tool to move around documents, not a complicated and slow-to-use bookmark system ala MS Word. That is, for example: I am writing some proof and I would like to check or modify something written in other part of the text (e.g., assumption section). With bookmarks available, press a keyboard shortcut for setting a bookmark; then move around, make changes, whatever...; press a keyboard shortcut to return to the previously set bookmark. Why a special solution, when labels and references exist? - bookmarks are meant just to speed up editing - it is enough to have one bookmark (or three?); thus, it is not necessary to bother user with a dialog to set the name of a bookmark and another one to choose a bookmark to go to --> it is fast - bookmarks does not place any object in the text, there is nothing to remove, when you no longer need a bookmark - bookmarks does not have to be stored (in the document file), they are just temporary within one editing session Of course, I do not know how LyX handles documents internally, so I have no idea whether it is complicated to implement bookmarks or not. Therefore, if there are more people who thinks that bookmarks might be useful and it is not too complicated, please, implement them. Otherwise, just forget it or put it somewhere on TO DO list with a low priority. > Would it be possible to implement bookmarks (at least one), please? > You can use Notes for this (you can bind, for example, Ctrl+j to note-next). Unfortunately, this does not work very well for me as I use Notes quite often in my documents. Best regards, Pavel Cizek
Re: lyx, natbib and alternate \cite commands
> Let's see how it works in 1.2.0cvs first. Fair point. Here is the patch. Visible changes: * Adds a "Use Natbib" check button to the Document dialog (tab Extra). * When natbib is enabled, the Citation dialog has a choice for the \citeX command. * I threw in the Browse Button in Print Dialog patch, because it's small, has no issues associated and I couldn't be bothered separating it out. Issues: * Toggling the "Use Natbib" button does not update the Citation dialog. The dialog must be closed/opened again (or the Restore button pressed if active). * Toggling "Use Natbib" Off will not change the LaTeX output from \citet, \citep etc to \cite. Ie, the output will be incorrect. You'll have to open/close each Citation inset by hand. * Cannot input comments before the citation when in natbib mode. The InsetCommandParams::options field must be altered to take multiple options before this can occur. Thoughts: make options a vector and access is with void setOption(string, int = 0) string getOption(int = 0) ie, behaviour is identical for most insets, but those that want multiple options can have 'em. No idea about how to output this to the LyX file. Any ideas? Finally: I'm not at all sure that I've done the use_natbib stuff correctly. Basically, I just copied use_amsmath. It all seems to work, but if someone in the know would check this over, I'd be very grateful. Angus patch.diff.bz2
Re: Another book written using LyX
> "Mike" == <[EMAIL PROTECTED]> writes: Mike> On Wed, 17 Jan 2001, Alejandro Aguilar Sierra wrote: >> Did anybody know about this book on postgresql? >> >> http://www.postgresql.org/docs/awbook.html >> >> IMHO the link should be somewhere in the users site, in a section >> "Who uses LyX". There should be also some other success stories >> that have been sent to this list, like Garst's ones. Mike> Ahem. It's in the FAQ - Section 1.2 "That's fine, but is it Mike> useful?". It's time to get the @#$% FAQ on the web page. Anyone Mike> want to make a whizzy thing to update an HTML page automatically Mike> when I update the LyX file in CVS? You mean here? http://www.sad.it/~jug/lyx/lyxdoc/FAQ/node2.html#SECTION00022000 I do not know how often it is updated, though. JMarc
Re: fax support, dead keys and i18n (1.1.6)
> "Thorsten" == Thorsten Mika <[EMAIL PROTECTED]> writes: Thorsten> i do not use a keymap. i see the acute and the grave, but Thorsten> they are strangely enough in the middle of the line Thorsten> (vertical) and not above the rest...any other idea? Are things better if you use another screen font (something standard like "-*-times")? JMarc
TUI volunteers
Hi all, now that 1.1.6 is closer to GUII and we have task forces for GNOME and KDE ports, I would like to raise your attention to the fact that we can do a TUI (Text-bases User Interface) and do it perfectly workable and enjoyable... In a world of antialiased fonts and annoying multicolor banners, the console is still one of the best mediums to get the job done: either it's better for our eyes on that laptop. it's workable through telnet and similar from a WIn machine w/o an X server, it must be faster to fire up (eg. a quick correction before printing/expoerting) and does not need X, which is okay but can be too much... Some time ago we talked about the TUI and some people showed interest. I think this is a good time to address the issue once more and see who's interested... I guess our best bet would be some ncurses or slang, although I know there must be other very good console toolkits, so let's talk... Whatever we choose, it's better/faster if it has some C++ wrappers so we can integrate it with the code directly and easily, if not, maybe some wrap up OO lib around the C one could be in order, so we get TUI toolkit independence as well (a kind of three layered system, C toolkit || Wrap up TUI API || LyX kernel) Anyone interested in this 'port'? laters and thanks, david PS- I am not subscribed for this list has too high a traffic profile for my mailer, so if you add me in the reply-to: header it's better, but I can access the list through the archives, so it's not necessary for you to bother... thn --- Get free personalized email at http://www.iname.com
Re: lyx-1.16 on hpux
> "Klaus" == Klaus Dittrich <[EMAIL PROTECTED]> writes: Klaus> OS: hpux-10.20 with both aCC an gcc-2.75.2 installed. I tried Klaus> to get lyx-1.16 up, here my expieriences .. Klaus> In ./src/support/fmt.C --- I had to insert Klaus> the declaration of vsnprintf in string fmt(char const * fmtstr Klaus> ...) extern int vsnprintf(char *, size_t, const char *, Klaus> va_list); to get it compiled. Seems configure doesn't configure Klaus> HAVE_SNPRINTF properly. Where is vsnprintf defined in HP-UX headers? I do not understand why the configure test compiles correctly, but not the fmt.C file. JMarc
Creating lyx mailing lists for other national languages?
I am currently looking at creating a lyx-fr mailing list to create a viable french LyX community (the main goal is to help the i18n projects). For the sake of consistency (and of my own laziness :), I'd like to create [EMAIL PROTECTED] Thus my questions are: 1/ Mate, are you willing to set this up? 2/ Should we create other lists for other languages? Are there some already existing lists like that? JMarc
Re: TUI volunteers
> "excalibor" == excalibor <[EMAIL PROTECTED]> writes: excalibor> Hi all, now that 1.1.6 is closer to GUII and we have task excalibor> forces for GNOME and KDE ports, I would like to raise your excalibor> attention to the fact that we can do a TUI (Text-bases User excalibor> Interface) and do it perfectly workable and enjoyable... That would be fun, indeed, but I think we still heavily rely on X. excalibor> I guess our best bet would be some ncurses or slang, excalibor> although I know there must be other very good console excalibor> toolkits, so let's talk... Is borland TurboVision good? I only know the pascal version, and it allows for all the usual GUI gizmos. It is a C++ library and is public domain, AFAIK. JMarc
Re: New feature: Bookmarks in LyX?
Pavel Cizek <[EMAIL PROTECTED]> writes: | Jean-Marc Lasgouttes wrote: | | > > "Pavel" == Pavel Cizek <[EMAIL PROTECTED]> writes: | > | > Pavel> However, I am missing a support for bookmarks in LyX, that is a | > Pavel> possibility to set a bookmark (mark a specific place in a | > Pavel> document) and to go to a previously set bookmark (return to the | > Pavel> marked place in the document later). I know there are many | > Pavel> possibilities how one can move around a LyX document (jump to | > Pavel> sections, references, etc.), but sometimes they just does not | > Pavel> work so well (= fast) for me like true bookmark would do. | > | > What about using labels for that? The note inset should be renamed InsetBookmark, a menu item with the list of bookmarks added and a way to id the bookmarks. So that they can be easily moved/jumped to. That is my option. We should have two kindos of bookmars, the default non-peristent ones, and the persistent one.s the non persistent lives only until you kill the document buffer (close) the persistent one lives in the file. Lgb
Re: lyx, natbib and alternate \cite commands
Angus Leeming <[EMAIL PROTECTED]> writes: | > Let's see how it works in 1.2.0cvs first. | | Fair point. | | Here is the patch. Visible changes: | * Adds a "Use Natbib" check button to the Document dialog (tab Extra). I'd rather hide this from the user (and I really want to get rid of the extra stuff). | * When natbib is enabled, the Citation dialog has a choice for the \citeX | command. Those commands should be renamed no "\citeX" anything should ever be visible to the user. | * I threw in the Browse Button in Print Dialog patch, because it's |small, has no issues associated and I couldn't be bothered |separating it out. Please bother. | Issues: | * Toggling the "Use Natbib" button does not update the Citation dialog. The | dialog must be closed/opened again (or the Restore button pressed if active). | | * Toggling "Use Natbib" Off will not change the LaTeX output from \citet, | \citep etc to \cite. Ie, the output will be incorrect. You'll have to | open/close each Citation inset by hand. So this should not be fixed in the inset, but discovered upon writeout. | * Cannot input comments before the citation when in natbib mode. The | InsetCommandParams::options field must be altered to take multiple options | before this can occur. Thoughts: | | make options a vector and access is with | void setOption(string, int = 0) | string getOption(int = 0) hmm, why the int? use a map instead. Look in Variables.C. | ie, behaviour is identical for most insets, but those that want multiple | options can have 'em. No idea about how to output this to the LyX file. Any | ideas? | | Finally: | | I'm not at all sure that I've done the use_natbib stuff correctly. Basically, | I just copied use_amsmath. It all seems to work, but if someone in the know | would check this over, I'd be very grateful. A branch to do this in would probably be nice. Lgb
Re: Creating lyx mailing lists for other national languages?
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | I am currently looking at creating a lyx-fr mailing list to create a | viable french LyX community (the main goal is to help the i18n | projects). For the sake of consistency (and of my own laziness :), I'd | like to create [EMAIL PROTECTED] Thus my questions are: Or I can host it on baywatch/aussie, but then you don't get lists.lyx.org. Then you could be the list admin yourself. Lgb
Re: TUI volunteers
Unfortunately, the GUII only means that the dialog are not dependent on X directly. The main work area is till X dependent, this is a pretty large task to tackle, there is supposedly the Painter class, but too much of LyX depends on Painter itself and not PainterBase. In short, the time is not ripe yet for a TUI, maybe in a version or two we'll be more prepared for this. -- Baruch Even http://baruch.ev-en.org/ (My Site) http://www.redrival.com/jindor/ (My brothers AD site) " Learn to laugh ... it's the path to true love! " - The Angel in the movie Michael
Re: Creating lyx mailing lists for other national languages?
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | I Lars> am currently looking at creating a lyx-fr mailing list to create Lars> a | viable french LyX community (the main goal is to help the Lars> i18n | projects). For the sake of consistency (and of my own Lars> laziness :), I'd | like to create [EMAIL PROTECTED] Thus my Lars> questions are: Lars> Or I can host it on baywatch/aussie, but then you don't get Lars> lists.lyx.org. Then you could be the list admin yourself. Of course [EMAIL PROTECTED] would be fine too, but I thought it would be better to integrate everything, epsecially if lists like lyx-de or lyx-no get created... JMarc
Re: lyx, natbib and alternate \cite commands
On Thu, Jan 18, 2001 at 10:07:26AM +, Angus Leeming wrote: > Yes, a little. I have preliminary natbib support working in my tree. I'd just > like to sort out how LyX stores options to LaTeX commands before releasing > this to the general public. > > Natbib can have up to two options in a \cite field; comments before and after > the citation. LyX can currently deal only with one. To accomodate two is an > ugly and extremely fragile hack. > > Hmmm. Thinking. I COULD ignore the extra options for the time being and just > release a simple patch that gives users the ability to input different \cite > commands. It wouldn't break future compatibility. Are people interested? > > What do people on the devel list think? I think the core folks need to discuss handling optional arguments. Unless they have already. I've mentioned before that not taking optional arguments (in \section, \caption, etc.) is one of a very few things that keep LyX from being fully compatible with RevTeX (American Physical Society's class) and other group's classes. Which is too bad, because these groups would be a great source of new users: professors and grad students who are afraid to use plain LaTeX. Wouldn't it be nice to have a link to lyx.org from aps.org etc.? Natbib is (according to Mike) the other reason for not suggesting LyX to large organizations. If you've got it working except for optargs, then that's another reason to have a discussion about optargs. Now that you've got the NEW_INSETS working, it's possible to add optarg support, right? Apologies for doing all this ranting when I won't be doing any of the coding. :( -Amir
Re: lyx, natbib and alternate \cite commands
Amir Karger <[EMAIL PROTECTED]> writes: | large organizations. If you've got it working except for optargs, then | that's another reason to have a discussion about optargs. Now that you've | got the NEW_INSETS working, it's possible to add optarg support, | right? NEW_INSETS are not quite there yet, so check it out (pun intended) and help finish the last (I believe) few problems. (I will hopefully have some time this weekend.) Lgb
Re: lyx, natbib and alternate \cite commands
Lars,
can I make one point here. This is preliminary work. Nobody was suggesting
that it would be the best possible way.
Right. Now I've said that, I'll answer your points.
> | * Adds a "Use Natbib" check button to the Document dialog (tab Extra).
> I'd rather hide this from the user (and I really want to get rid of
> the extra stuff).
This means that natbib will always be used. Is this what you want? Why?
Moreover, the \usepackage{natbib} command can take a raft of options. This
should go in the Document dialog somewhere, probably in it's own, dedicated
tab folder.
> | * When natbib is enabled, the Citation dialog has a choice for the \citeX
> | command.
> Those commands should be renamed no "\citeX" anything should ever be
> visible to the user.
Whilst I see that I could use two checkboxes to go from \citeX to \citeX* or
from \citeX to \CiteX, natbib supports so many different \citeX commands that
I really can't see how better to do this. Anyway, the principle point
remains. This is preliminary work.
> | * Toggling "Use Natbib" Off will not change the LaTeX output from \citet,
> | \citep etc to \cite. Ie, the output will be incorrect. You'll have to
> | open/close each Citation inset by hand.
>
> So this should not be fixed in the inset, but discovered upon
> writeout.
Yes, this is what I've just done. Overload the InsetCite::Latex() method.
However, if we ALWAYS use natbib, then the code isn't needed. So, the "design
argument" should be thrashed out.
> | * Cannot input comments before the citation when in natbib mode.
> | The InsetCommandParams::options field must be altered to take
> | multiple options before this can occur. Thoughts:
> |
> | make options a vector and access is with
> | void setOption(string, int = 0)
> | string getOption(int = 0)
>
> hmm, why the int? use a map instead.
> Look in Variables.C.
My turn to hmm. Not sure I understand you. A generic latex command can take
multiple options
\cmdname [option1] [option2] [option X] {contents}
why would a map represent this concept more cleanly? Are you talking about
using a map to store the data rather than a vector? But this is an
implementation detail, not an interface one.
> | I'm not at all sure that I've done the use_natbib stuff correctly.
> | Basically, I just copied use_amsmath. It all seems to work, but if
> | someone in the know would check this over, I'd be very grateful.
>
> A branch to do this in would probably be nice.
Ok. Will this work: (and do I have write permission?)
To create a branch of lyx-devel
===
1. create a tag at the current point
cvs tag natbib-TAG lyx-devel
2. create a branch tag on that tag
cvs rtag -b -r natbib-TAG natbib-BRANCH lyx-devel
3. checkout
cvs checkout -r natbib-BRANCH
4. apply my changes to this checked out code
patch -p0 < patch_natbib
5. commit the changes
cvs commit
Angus
Re: lyx, natbib and alternate \cite commands
On Thu, Jan 18, 2001 at 03:46:46PM +0100, Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: > | Here is the patch. Visible changes: > | * Adds a "Use Natbib" check button to the Document dialog (tab Extra). > > I'd rather hide this from the user (and I really want to get rid of > the extra stuff). But perhaps we do need a citation tab in the Document dialog which will contain the bibilography-style (this should not be stored in the bibtex inset), citation mode (author-year/numerical) and the citation style. I do agree that the decision whether to use natbib should be made by LyX. > | I'm not at all sure that I've done the use_natbib stuff correctly. Basically, > | I just copied use_amsmath. It all seems to work, but if someone in the know > | would check this over, I'd be very grateful. > > A branch to do this in would probably be nice. I think that there are too few changes here to require a branch.
Re: New feature: Bookmarks in LyX?
On 18 Jan 2001, Lars Gullik Bjønnes wrote: > The note inset should be renamed InsetBookmark, a menu item with the > list of bookmarks added and a way to id the bookmarks. So that they > can be easily moved/jumped to. > > That is my option. > > We should have two kindos of bookmars, the default non-peristent ones, > and the persistent one.s The persistent ones are already called "labels" and there are already ways to navigate between references (goto and return). Alejandro
Re: New feature: Bookmarks in LyX?
Alejandro Aguilar Sierra <[EMAIL PROTECTED]> writes: | On 18 Jan 2001, Lars Gullik Bjønnes wrote: | | > The note inset should be renamed InsetBookmark, a menu item with the | > list of bookmarks added and a way to id the bookmarks. So that they | > can be easily moved/jumped to. | > | > That is my option. | > | > We should have two kindos of bookmars, the default non-peristent ones, | > and the persistent one.s | | The persistent ones are already called "labels" and there are already ways | to navigate between references (goto and return). No. The persisten ones are today called "Notes" and there are no way to navigate quickly beween them or to them. Lgb
Re: lyx, natbib and alternate \cite commands
Dekel Tsur <[EMAIL PROTECTED]> writes: | On Thu, Jan 18, 2001 at 03:46:46PM +0100, Lars Gullik Bjønnes wrote: | > Angus Leeming <[EMAIL PROTECTED]> writes: | > | Here is the patch. Visible changes: | > | * Adds a "Use Natbib" check button to the Document dialog (tab Extra). | > | > I'd rather hide this from the user (and I really want to get rid of | > the extra stuff). | | But perhaps we do need a citation tab in the Document dialog which will | contain the bibilography-style (this should not be stored in the bibtex | inset), citation mode (author-year/numerical) and the citation style. | I do agree that the decision whether to use natbib should be made by LyX. | | > | I'm not at all sure that I've done the use_natbib stuff correctly. Basically, | > | I just copied use_amsmath. It all seems to work, but if someone in the know | > | would check this over, I'd be very grateful. | > | > A branch to do this in would probably be nice. | | I think that there are too few changes here to require a branch. A branch to "finish" the support for natbib, not to add this preliminary patch. Lgb
Re: New feature: Bookmarks in LyX?
a long, long time ago... We were having this self-same discussion. I wrote a new InsetNote. It did nothing but replace InsetInfo with GUI-I and NEW_INSET code. Shall I resubmit it again now that NEW_INSETs are go? It'll provide the starting point for some real work on this. I seem to remember that at the time we defined THREE possible notes. It's all in the archives... Also note that Jean-Marc and Dekel have both proposed a general gotoInset dialog analogous to the Find dialog for text. Angus On Thursday 18 January 2001 15:47, Lars Gullik Bjønnes wrote: > Alejandro Aguilar Sierra <[EMAIL PROTECTED]> writes: > > | On 18 Jan 2001, Lars Gullik Bjønnes wrote: > | > | > The note inset should be renamed InsetBookmark, a menu item with the > | > list of bookmarks added and a way to id the bookmarks. So that they > | > can be easily moved/jumped to. > | > > | > That is my option. > | > > | > We should have two kindos of bookmars, the default non-peristent ones, > | > and the persistent one.s > | > | The persistent ones are already called "labels" and there are already ways > | to navigate between references (goto and return). > > No. The persisten ones are today called "Notes" and there are no way > to navigate quickly beween them or to them. > > Lgb
Re: lyx, natbib and alternate \cite commands
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars,
| can I make one point here. This is preliminary work. Nobody was suggesting
| that it would be the best possible way.
I know that.
| Right. Now I've said that, I'll answer your points.
|
| > | * Adds a "Use Natbib" check button to the Document dialog (tab Extra).
| > I'd rather hide this from the user (and I really want to get rid of
| > the extra stuff).
|
| This means that natbib will always be used. Is this what you want?
| Why?
No, LyX knows if natbib is available. and use it if present, if
features is used that we can't do with out we give a warning and use a
working non-optimal solution instead.
| Moreover, the \usepackage{natbib} command can take a raft of options. This
| should go in the Document dialog somewhere, probably in it's own, dedicated
| tab folder.
The options:
- text before [abc][]
- text after [abc]
(- text before and after [abc][abc])
- full name
- with parantesis
- mode author-year/numerical
These are the options in 4.2 in the natbib doc.
The options in 4.3. should also be supported, but not absolutely for
the first implementation.
All of this should be possible to set in .layout and in
Document->Citation, however individual style on each InsetCitation
should also be possible. Pluss separate config of the Bibliography
style (the list of references.)
| > | * When natbib is enabled, the Citation dialog has a choice for the \citeX
| > | command.
|
| > Those commands should be renamed no "\citeX" anything should ever be
| > visible to the user.
|
| Whilst I see that I could use two checkboxes to go from \citeX to \citeX* or
| from \citeX to \CiteX, natbib supports so many different \citeX commands that
| I really can't see how better to do this. Anyway, the principle point
| remains. This is preliminary work.
And don't try to support everything at once, select the most needed
subset.
| > hmm, why the int? use a map instead.
| > Look in Variables.C.
|
| My turn to hmm. Not sure I understand you. A generic latex command can take
| multiple options
|
| \cmdname [option1] [option2] [option X] {contents}
|
| why would a map represent this concept more cleanly? Are you talking about
| using a map to store the data rather than a vector? But this is an
| implementation detail, not an interface one.
We are not talking generig latex commands here... And I do not reallt
se how citation really plays in (but we solve it by having insets in
insets.)
| Ok. Will this work: (and do I have write permission?)
No, not yet, You did not take part in the "what dir do yo uneed write
permissions to" discussion.
| To create a branch of lyx-devel
You really should read the doc I posted a while ago.
| ===
| 1. create a tag at the current point
| cvs tag natbib-TAG lyx-devel
I belive it was TAG_CREATE_natbib
| 2. create a branch tag on that tag
| cvs rtag -b -r natbib-TAG natbib-BRANCH lyx-devel
BRANCH_natbib
| 3. checkout
| cvs checkout -r natbib-BRANCH
or from inside your already checked out dir:
cvs update -r BRANCH_natbib
| 4. apply my changes to this checked out code
| patch -p0 < patch_natbib
if as above:
cvs update
cvs commit
Lgb
Re: New feature: Bookmarks in LyX?
Angus Leeming <[EMAIL PROTECTED]> writes: | We were having this self-same discussion. I wrote a new InsetNote. It did | nothing but replace InsetInfo with GUI-I and NEW_INSET code. Shall I resubmit | it again now that NEW_INSETs are go? Yes, but against the NEW_INSET branch. | It'll provide the starting point for | some real work on this. I seem to remember that at the time we defined THREE | possible notes. It's all in the archives... Care to spare me the digging? | Also note that Jean-Marc and Dekel have both proposed a general gotoInset | dialog analogous to the Find dialog for text. I am not sure if this will cut it. We want to ge able to move quickly to InsetBookmark named: "1" (and no dialog should be needed) Lgb
Re: Two ideas
On Tue, Jan 16, 2001 at 04:33:51PM -0600, Brett Jones wrote: > When using nested bullets, etc., it seems to me that when increasing the > depth of a bullet, all bullets nested beneath that bullet should also be > bumped down a level. Of course, bumping up against the maximum depth > would be a special case. Also, just my opinion, but I would think it > more intuitive to stay at the current depth when hitting return on a > bullet, rather than explicitly having to hit M-Return. Jumping back up > a level should have to be explicit imho. I agree with the above. However, is there a future plan to replace the current paragraph layout mechanism by insets ? (namely, we will have enumerate inset, section inset etc).
Re: Displaystyle
On Tue, Jan 16, 2001 at 02:21:31PM +0100, Hartmut S. Leipner wrote:
> I cannot change the size of parts of an equation by setting displaystyle. At
> a first glance it seems to work. However after saving and reopening the file
> all special size settings are gone. This does not work neither with the input
> in the minibuffer (math-size displaystyle) nor by direct input in tex code
> (\displaystyle).
I think that the mathed sometimes get confused with font changing commands,
namely, this is a bug.
One way to cope with this bug is to put
\newcommand{\dstyle}[1]{\displaystyle{#1}}
in the preamble, and use the \dstyle command in the mathed.
Re: lyx, natbib and alternate \cite commands
> No, not yet, You did not take part in the "what dir do yo uneed write > permissions to" discussion. Perhaps this was whilst my computer was belly side -up? > You really should read the doc I posted a while ago. If I could find it, I would. Can you remember it's title or such like? > | 1. create a tag at the current point > | cvs tag natbib-TAG lyx-devel > > I belive it was TAG_CREATE_natbib I'm glad I got this mail before proceeding further. Ok, before I cook my goose and piss everybody off. I have just typed from my own top directory of lyx-devel (plase note that this is EXACTLY what I typed): cvs tag natbib-TAG to get [EMAIL PROTECTED]'s password: T .cvsignore T ABOUT-NLS T ANNOUNCE etc and cvs rtag -R -b -r natbib-TAG natbib-BRANCH lyx-devel to get [EMAIL PROTECTED]'s password: cvs server: Tagging lyx-devel cvs server: Tagging lyx-devel/boost etc. So it appears that I do have write access? I was about to type cvs update cvs commit when I recieved your mail, Lars. However, if I've done this incorrectly, can you tell me how to undo it? I'll wait to hear from you before doing anything further. Angus > > | 2. create a branch tag on that tag > | cvs rtag -b -r natbib-TAG natbib-BRANCH lyx-devel > > BRANCH_natbib > > | 3. checkout > | cvs checkout -r natbib-BRANCH > > or from inside your already checked out dir: > > cvs update -r BRANCH_natbib > > | 4. apply my changes to this checked out code > | patch -p0 < patch_natbib > > if as above: > > cvs update > cvs commit > > Lgb
Re: Two ideas
Dekel Tsur <[EMAIL PROTECTED]> writes: | I agree with the above. | However, is there a future plan to replace the current paragraph layout | mechanism by insets ? (namely, we will have enumerate inset, section inset | etc). Yes, at least I want to do that. Especially the lists. They are really cluttering up LyXText Lgb
Re: Two ideas
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes: Dekel> I agree with the above. However, is there a future plan to Dekel> replace the current paragraph layout mechanism by insets ? Dekel> (namely, we will have enumerate inset, section inset etc). I'd like to avoid that. The idea I have been advocating is to keep the main text as a paragraph, but use insets as needed (the \item of a list, the optional argument of section...). Juergen said at the time he has ideas on how to do that. JMarc
Re: TUI volunteers
Hi all, Jean-Marc wrote: > That would be fun, indeed, but I think we still heavily rely on X. Nod... but we can start preparing for the day we're free :) After all, the GNOME/KDE task forces are already working on it... > excalibor> I guess our best bet would be some ncurses or slang, > excalibor> although I know there must be other very good console > excalibor> toolkits, so let's talk... > > Is borland TurboVision good? I only know the pascal version, and it > allows for all the usual GUI gizmos. It is a C++ library and is public > domain, AFAIK. It's GPL, nod... I've downloaded version 0.6 to evaluate it... Also found Terminality (http://members.optushome.com.au/darkmoon7/term.html) it uses ncurses but looks pretty stable and usable... some of the screens are cool (and the API is similar to the Borland one) Maybe the best would be to wrap the TUI capability in a thin layer so it can be built either with ncurses, s-lang, or any of the other useful packages... It may be not too difficult (obviously, requiring one of the non-usual libraries will make it harder for people to use...) Someone interested in having a look at how this could possibly be made? I haven't checked the GUII code... (actually haven't downloaded 1.1.6, it's not in the ftp server (?)) best regards, david --- Get free personalized email at http://www.iname.com
Re: New feature: Bookmarks in LyX?
On Thursday 18 January 2001 16:25, Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: > > | We were having this self-same discussion. I wrote a new InsetNote. It did > | nothing but replace InsetInfo with GUI-I and NEW_INSET code. Shall I resubmit > | it again now that NEW_INSETs are go? > > Yes, but against the NEW_INSET branch. Oh, Lordy. I need to read that article! > | It'll provide the starting point for > | some real work on this. I seem to remember that at the time we defined THREE > | possible notes. It's all in the archives... > > Care to spare me the digging? http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg14517.html So, care to reciprocate the favour and tell me wherre to find your cvs article? > > | Also note that Jean-Marc and Dekel have both proposed a general gotoInset > | dialog analogous to the Find dialog for text. > > I am not sure if this will cut it. We want to ge able to move quickly > to InsetBookmark named: "1" > (and no dialog should be needed) > > Lgb
Re: lyx, natbib and alternate \cite commands
On 18 Jan 2001, Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: > > | Right. Now I've said that, I'll answer your points. > | > | > | * Adds a "Use Natbib" check button to the Document dialog (tab Extra). > | > I'd rather hide this from the user (and I really want to get rid of > | > the extra stuff). > | > | This means that natbib will always be used. Is this what you want? > | Why? > > No, LyX knows if natbib is available. and use it if present, if > features is used that we can't do with out we give a warning and use a > working non-optimal solution instead. > > Lgb > LyX knows if natbib is available at the current installation. But suppose I want to export-to-LaTeX and share the file with someone? There must be some way to ignore the idiosyncrasies of a particular installation. Lior.
Re: New feature: Bookmarks in LyX?
On Thu, 18 Jan 2001, Pavel Cizek wrote: [snip] > My idea was to have a simple tool to move around documents, not a > complicated and slow-to-use bookmark system ala MS Word. That is, for > example: I am writing some proof and I would like to check or modify > something written in other part of the text (e.g., assumption > section). With bookmarks available, press a keyboard shortcut for > setting a bookmark; then move around, make changes, whatever...; press > a keyboard shortcut to return to the previously set bookmark. > [snip] > Best regards, > > Pavel Cizek > > > It seems you want to be able to set a single bookmark, and then get there with a keypress. This bookmark can be easily moved (just set it somewhere else). The discussion seems to focus on adding/adapting support for multiple bookmarks you can cycle through with a keypress, so you have to explicitely remove them when you don't need them (or by closing the file). Which of the two is preferable ? Lior.
Re: lyx, natbib and alternate \cite commands
On Thu, Jan 18, 2001 at 03:34:27PM +, Angus Leeming wrote: > > > | * When natbib is enabled, the Citation dialog has a choice for the \citeX > > | command. > > > Those commands should be renamed no "\citeX" anything should ever be > > visible to the user. > > Whilst I see that I could use two checkboxes to go from \citeX to \citeX* or > from \citeX to \CiteX, natbib supports so many different \citeX commands that > I really can't see how better to do this. Anyway, the principle point > remains. This is preliminary work. Word's Date popup gives you a bunch of possible options. You could do the same in the cite popup: Format: (Jones et al. 1990) Jones et al. (1990) Jones, Baker, and Williams (1990) Jones et al. 1990 Jones et al. 1990 Of course, if the person had selected to use numerical references, you would want this to show up as Jones et al. [2] [2] etc. Of course, this depends on whether the user selected numbers or authoryear for their citations. I don't know whether you'd want to have the default outlined or have it greyed out with a checkbox for "special citation" or some such. -Amir
Re: lyx, natbib and alternate \cite commands
Angus Leeming <[EMAIL PROTECTED]> writes: | > No, not yet, You did not take part in the "what dir do yo uneed write | > permissions to" discussion. | | Perhaps this was whilst my computer was belly side -up? Or perhaps because you were not on that mailinglist... | > You really should read the doc I posted a while ago. | If I could find it, I would. Can you remember it's title or such like? "Better use of CVS" or something | > | 1. create a tag at the current point | > | cvs tag natbib-TAG lyx-devel | > | > I belive it was TAG_CREATE_natbib | | I'm glad I got this mail before proceeding further. | Ok, before I cook my goose and piss everybody off. | | I have just typed from my own top directory of lyx-devel (plase note that | this is EXACTLY what I typed): | cvs tag natbib-TAG | to get | [EMAIL PROTECTED]'s password: | T .cvsignore | T ABOUT-NLS | T ANNOUNCE | etc | | and | cvs rtag -R -b -r natbib-TAG natbib-BRANCH lyx-devel | to get | [EMAIL PROTECTED]'s password: | cvs server: Tagging lyx-devel | cvs server: Tagging lyx-devel/boost | etc. | | So it appears that I do have write access? | I was about to type | cvs update | cvs commit | when I recieved your mail, Lars. You were to quick with this. You are no followin ghte naming standard for tags. | However, if I've done this incorrectly, can you tell me how to undo it? I'll | wait to hear from you before doing anything further. Just remove the tags you added with : cvs rtag -d lyx-devel (the branch first then the other) Lgb
