Re: Assigning keyboard shortcut to 3rd level menu item
On 08/12/2017 05:25 PM, Rich Shepard wrote: On Sat, 12 Aug 2017, Paul A Rubin wrote: Curious. Your setup must be a tad nonstandard. Paul, Could be ... because I am. Ain't we all! I tested it at my end (using " pdf2") and it worked. In the list of file formats (under preferences) on both my machines, pdf2 is "shorthand" for "PDF (pdflatex)". That's a LyX default, not something I screwed with. Hmmm-m-m. Under Tools -> Preferences -> File Handling -> File formats for default output formats with TeX fonts PDF (pdflatex), with non-TeX fonts DVI (LuaTeX). The Shortcut text entry widget is empty. I use the T1 TeX font encoding; the default body text typeface is Palatino. Same one mine, but that's not the key bit. And, in hindsight, it's possible I gave you the way to export to the wrong format. Under Tools > Preferences > File Handling > File formats, click on the Format select box at the top and scroll to "LaTeX (pdflatex)". I suspect that under "Short name" you have "pdflatex", as I do. Now switch the select box to "PDF (pdflatex)", and I suspect the short name is now "pdf2". At least it is on my systems. So I gave you the shortcut to export the buffer as a PDF file, compiled using pdflatex, which might not be what you had in mind. What worked for you should be producing a LaTeX source file compatible with pdflatex. If that's what you want, dandy. The expression of confusion by LyX when you used "pdf2" suggests that maybe it doesn't know how to compile to PDF using pdflatex (converter not specified, didn't find pdflatex on your system, finds pdflatex morally objectionable, thinks it's a Russian plot/Chinese hoax/SNL skit, ...). Paul
Re: Assigning keyboard shortcut to 3rd level menu item
On Sat, 12 Aug 2017, Paul A Rubin wrote: Curious. Your setup must be a tad nonstandard. Paul, Could be ... because I am. I tested it at my end (using " pdf2") and it worked. In the list of file formats (under preferences) on both my machines, pdf2 is "shorthand" for "PDF (pdflatex)". That's a LyX default, not something I screwed with. Hmmm-m-m. Under Tools -> Preferences -> File Handling -> File formats for default output formats with TeX fonts PDF (pdflatex), with non-TeX fonts DVI (LuaTeX). The Shortcut text entry widget is empty. I use the T1 TeX font encoding; the default body text typeface is Palatino. Rich
Re: Assigning keyboard shortcut to 3rd level menu item
On 08/12/2017 03:26 PM, Rich Shepard wrote: I selected buffer-export with the chord Ctrl-X H, clicked modify, and added ' pdf2'. Clicked the OK and Save buttons. When I tested it the status bar said, 'don't know how to export format.' But, ... changing ' pdf2' to ' pdflatex' works. Curious. Your setup must be a tad nonstandard. I tested it at my end (using " pdf2") and it worked. In the list of file formats (under preferences) on both my machines, pdf2 is "shorthand" for "PDF (pdflatex)". That's a LyX default, not something I screwed with. Paul
Re: Assigning keyboard shortcut to 3rd level menu item
On Sat, 12 Aug 2017, Paul A. Rubin wrote: It's not entirely intuitive IMHO. Paul, You win this week's understatement award. Start out doing what you were doing (clicking Modify, assigning the chord), but before committing the key assignment put the cursor in the text field next to "buffer-export" and add " pdf2" including the leading space. I selected buffer-export with the chord Ctrl-X H, clicked modify, and added ' pdf2'. Clicked the OK and Save buttons. When I tested it the status bar said, 'don't know how to export format.' But, ... changing ' pdf2' to ' pdflatex' works. Thanks very much, Rich
Re: Assigning keyboard shortcut to 3rd level menu item
On 08/12/2017 12:49 PM, Rich Shepard wrote: I'm certain this can be done, but since I've not yet done so I'm not sure how to proceed. In Preferences -> Editing -> Shortcuts -> Document and Window I see 'buffer-export' has two chords: Ctrl-H (in plain font) and Ctrl-X H (in boldface font). Why? I don't know, but that's what's there. What I would like to do is assign Ctrl-X H to File -> Export -> pdflinux (or buffer-export-pdflinux). When I highlight 'buffer-export' and select the Modify button I'm not seeing a way to add the pdflinux as the default export format. A cluestick will help. Rich It's not entirely intuitive IMHO. Start out doing what you were doing (clicking Modify, assigning the chord), but before committing the key assignment put the cursor in the text field next to "buffer-export" and add " pdf2" including the leading space. It will create a new line in the command list, leaving buffer-export unchanged ... which is okay, since the buffer-export command by itself doesn't do anything (other than creating a status message something like "Say what, kemosabe?"). Paul
Assigning keyboard shortcut to 3rd level menu item
I'm certain this can be done, but since I've not yet done so I'm not sure how to proceed. In Preferences -> Editing -> Shortcuts -> Document and Window I see 'buffer-export' has two chords: Ctrl-H (in plain font) and Ctrl-X H (in boldface font). Why? I don't know, but that's what's there. What I would like to do is assign Ctrl-X H to File -> Export -> pdflinux (or buffer-export-pdflinux). When I highlight 'buffer-export' and select the Modify button I'm not seeing a way to add the pdflinux as the default export format. A cluestick will help. Rich
Re: LyX native format stuck in the middle
On Fri, 11 Aug 2017 09:23:06 +0100 José Abílio Matoswrote: > On Monday, 31 July 2017 18.30.31 WEST Steve Litt wrote: > > I know what I'm asking for is monsterously difficult, and I know I > > certainly don't have the technical chops to do it. But when it gets > > done, LyX will be a brand new world, finally living up to its > > promise of write once, deploy everywhere. > > > > Thanks, > > > > SteveT > > The main technical problems of this enterprise are the math insets. > Should they also be converted to an xml like format? Hi José, You ask two different questions: 1) Should math insets be well formed XML? 2) MUST math insets be well formed XML? To #1, yes, it would be nice, and then math insets could be handled via an XML parser. This is something we'd want to work toward at some point in the future. To #2, HECKNO! The perfect is the enemy of the good, so it would be silly to hold up the rest of the XMLization just for math insets. As long as you can encapsulate the math insets in an XML tag in a way that they won't cause an XML parser to choke or abort, that's wonderful: The XML parser can hand the application programmer the encasing XML node, and the application programmer can parse apart the math insets herhimself. SteveT