Re: adding a class to LyX from a "latex skeleton"
Thanks! I am actually rather faint of heart, but I'll have a go at it. On Nov 3, 2021, at 7:13 PM, Paul A. Rubin mailto:parubi...@gmail.com>> wrote: On 11/3/21 1:31 PM, David Pesetsky wrote: I would like to be able to create a LyX document using one of the “latex-skeletons” at https://langsci-press.org/templatesAndTools (specifically, at the moment, the “Latex-skeleton for monographs”) — but can’t seem to find a how-to for adding, say, a Langsci Press book class to LyX, or anything else useful. If there are relevant instructions somewhere, can you point me to them, or otherwise help? I’m using LyX 2.3 on a Mac — thanks! -David -- David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>] Department of Linguistics and Philosophy 32-D862 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html As a starting point, I would urge you to read section 5 of the customization manual (Help > Customization). You'll need to create a layout file for the new class (in this case, "langscibook.cls"). The recommended approach is usually to find a LaTeX class similar to the new one for which LyX has a layout file, then use that file as a guide when creating your own layout file. I'm inclined to describe the process as "not for the faint of heart", but it is doable (and has been done in the past). Paul -- lyx-users mailing list lyx-users@lists.lyx.org<mailto:lyx-users@lists.lyx.org> http://lists.lyx.org/mailman/listinfo/lyx-users - -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
adding a class to LyX from a "latex skeleton"
I would like to be able to create a LyX document using one of the “latex-skeletons” at https://langsci-press.org/templatesAndTools (specifically, at the moment, the “Latex-skeleton for monographs”) — but can’t seem to find a how-to for adding, say, a Langsci Press book class to LyX, or anything else useful. If there are relevant instructions somewhere, can you point me to them, or otherwise help? I’m using LyX 2.3 on a Mac — thanks! -David -- David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>] Department of Linguistics and Philosophy 32-D862 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: shortcut for going to edge of ERT frame?
Very helpful, thank you! > On Aug 8, 2021, at 3:12 PM, Paul A. Rubin wrote: > > On 8/8/21 2:01 PM, David Pesetsky wrote: >> Is there any way to program a key so that if you are typing within an ERT >> frame, it takes the cursor to the last (or first) character in that frame? >> >> Also useful would be a way to exit the frame — landing at at the first >> non-ERT character to the left or right of the frame. >> >> -David >> > You can bind keys to the functions "inset-begin" (positions the cursor before > the first character in the inset) and "inset-end" (positions the cursor after > the last character in the inset). In both cases, the cursor remains within > the inset. > > To exit the inset, you can use "command-sequence inset-end; char-forward;". > > Paul > > -- > lyx-users mailing list > lyx-users@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-users -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: shortcut for going to edge of ERT frame?
On Aug 8, 2021, at 2:09 PM, Chris Menzel mailto:chris.men...@gmail.com>> wrote: For me, Ctrl-a and Ctrl-e move the cursor in an ERT frame to the first and last characters of the frame, respectively. However, I'm not sure if this is because I'm using Emacs keybindings or because I'm using a Mac, which also uses those keybindings in text areas. Thanks for the reply! Unfortunately, no luck. I have been using the mac keybindings, plus some customizations. Unfortunately, neither with the mac keybindings nor when I change to the emacs keybindings (I was hoping to get the code that way) do I see these actions. With the mac keybindings, ctrl-e takes me to the end of the on-screen line, but not the end of the frame. Ctrl-a alone seems to do nothing except display "^a options" on the status bar at the bottom. With the emacs keybindings, both ctrl-a and ctrl-e yield "unknown function". Ctrl-o closes the frame and places the cursor to its immediate left; that behavior is definitely due to my choice of Emacs keybindings. Chris Menzel On Sun, Aug 8, 2021 at 1:01 PM David Pesetsky mailto:pese...@mit.edu>> wrote: Is there any way to program a key so that if you are typing within an ERT frame, it takes the cursor to the last (or first) character in that frame? Also useful would be a way to exit the frame — landing at at the first non-ERT character to the left or right of the frame. -David -- lyx-users mailing list lyx-users@lists.lyx.org<mailto:lyx-users@lists.lyx.org> http://lists.lyx.org/mailman/listinfo/lyx-users -- David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>] Department of Linguistics and Philosophy 32-D862 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
shortcut for going to edge of ERT frame?
Is there any way to program a key so that if you are typing within an ERT frame, it takes the cursor to the last (or first) character in that frame? Also useful would be a way to exit the frame — landing at at the first non-ERT character to the left or right of the frame. -David -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: find next?
I'm not seeing "<" or ">" on the buttons. -David On Feb 20, 2021, at 3:07 PM, Kornel Benko mailto:kor...@lyx.org>> wrote: Am Sat, 20 Feb 2021 19:53:20 + schrieb David Pesetsky mailto:pese...@mit.edu>>: Trying it out on 2.4.0 Alpha 3, it seems to work very well now, thank you again. But I am seeing two "Find" and two "Replace" buttons. Not a functionality problem — they both work — but presumably some kind of error. You mean probably ' < Find ' and ' Find > ' (means find backward and find forward) Same for 'replace' -David On Feb 12, 2021, at 10:24 AM, David Pesetsky mailto:pese...@mit.edu><mailto:pese...@mit.edu>> wrote: Pleased indeed, thank you!!! On Feb 12, 2021, at 10:14 AM, Jürgen Spitzmüller mailto:sp...@lyx.org><mailto:sp...@lyx.org>> wrote: Am Freitag, dem 12.02.2021 um 14:53 + schrieb David Pesetsky: If you click on the document window, the "find next" key (⌘-G ) will do its job and get you to the next occurrence of the search string. Without that, however, if focus remains in the Find window, nothing happens at all. That is what is non-intuitive. In most other apps, You can search for what you want with ⌘-F, and then simply pressing ⌘-G gets you the next occurrence, with no other steps necessary. You might be pleased to hear that your message inspired me to go ahead and fix that for 2.4.0 this morning. Jürgen Kornel -- lyx-users mailing list lyx-users@lists.lyx.org<mailto:lyx-users@lists.lyx.org> http://lists.lyx.org/mailman/listinfo/lyx-users -- David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>] Department of Linguistics and Philosophy 32-D862 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: find next?
Trying it out on 2.4.0 Alpha 3, it seems to work very well now, thank you again. But I am seeing two "Find" and two "Replace" buttons. Not a functionality problem — they both work — but presumably some kind of error. -David On Feb 12, 2021, at 10:24 AM, David Pesetsky mailto:pese...@mit.edu>> wrote: Pleased indeed, thank you!!! On Feb 12, 2021, at 10:14 AM, Jürgen Spitzmüller mailto:sp...@lyx.org>> wrote: Am Freitag, dem 12.02.2021 um 14:53 + schrieb David Pesetsky: If you click on the document window, the "find next" key (⌘-G ) will do its job and get you to the next occurrence of the search string. Without that, however, if focus remains in the Find window, nothing happens at all. That is what is non-intuitive. In most other apps, You can search for what you want with ⌘-F, and then simply pressing ⌘-G gets you the next occurrence, with no other steps necessary. You might be pleased to hear that your message inspired me to go ahead and fix that for 2.4.0 this morning. Jürgen -- David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>] Department of Linguistics and Philosophy 32-D862 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: find next?
Pleased indeed, thank you!!! On Feb 12, 2021, at 10:14 AM, Jürgen Spitzmüller mailto:sp...@lyx.org>> wrote: Am Freitag, dem 12.02.2021 um 14:53 + schrieb David Pesetsky: If you click on the document window, the "find next" key (⌘-G ) will do its job and get you to the next occurrence of the search string. Without that, however, if focus remains in the Find window, nothing happens at all. That is what is non-intuitive. In most other apps, You can search for what you want with ⌘-F, and then simply pressing ⌘-G gets you the next occurrence, with no other steps necessary. You might be pleased to hear that your message inspired me to go ahead and fix that for 2.4.0 this morning. Jürgen -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: find next?
I really appreciate all the replies. Jürgen's message is exactly what I discovered with more tinkering. If you click on the document window, the "find next" key (⌘-G ) will do its job and get you to the next occurrence of the search string. Without that, however, if focus remains in the Find window, nothing happens at all. That is what is non-intuitive. In most other apps, You can search for what you want with ⌘-F, and then simply pressing ⌘-G gets you the next occurrence, with no other steps necessary. -David https://www.lyx.org/trac/ticket/11170 Here, F3 does work, but only if I gave the workarea focus, which is not so apparent if you use the dialog. The working procedure is: 1. Ctrl-F 2. Enter search string 3. Hit Enter to fin first occurrence 4. Click into workarea OR close dialog 5. Hit F3 to find next occurrences I suspect 4. is the crucial missing step. I'll check if we can do something to avoid this unintuive extra step. Jürgen -- David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>] Department of Linguistics and Philosophy 32-D862 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
find next?
My Macintosh-educated fingers are used to ⌘-G for "find next" (used after using ⌘-F for "find"). Does Lyx have a "find next" function so I can duplicate this? I may be missing something in plain view, in which case, my apologies for wasting everyone's time — but I'm not finding it. -David -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: "LaTeX3 Error: Command '\textsi' not yet defined!"
FYI, I reported the bug to the developer, who replied:
Thanks. It looks like fontspec doesn’t define this any more. I’ll fix embrac.
In the meantime you can add to your preamble
\providecommand\textsi[1]{#1}
That should prevent the error.
Thank you for your help here.
-David
On Feb 16, 2020, at 2:10 PM, David Pesetsky
mailto:pese...@mit.edu>> wrote:
One final note: I have discovered that if I go to TexLive and change Configure
> Change Default Tex Live Version from "TeXLive-2019" to "TeXLive-2018", the
error and the "L3 Programming Layer" messages disappear. I hope that narrows
things down sufficiently.
-David
On Feb 16, 2020, at 11:49 AM, David Pesetsky
mailto:pese...@mit.edu>> wrote:
Before (June 2019, via MacOS Time Machine):
LyX 2.3.2
TexLive 1.35
MacOS Mojave (10.14.x)
Now
Lyx 2.3.4.2
TexLive 1.36
MacOS Catalina (10.15.3)
Minimal Working Example:
without embrac package:
with embrac package:
Without embrac, the file compiles successfully, but does display "L3
Programming Layer " while compiling (as does every Lyx file at the
moment).
Hope this gives you what you need to help, and many thanks in advance.
-David
On Feb 15, 2020, at 11:24 PM, Joel Kulesza
mailto:jkule...@gmail.com>> wrote:
On Sat, Feb 15, 2020 at 3:53 PM David Pesetsky
mailto:pese...@mit.edu>> wrote:
I was using Lyx for Mac rather extensively to write a long-ish manuscript about
a year ago, but have been away from it for a while.
In the interval, a problem has arisen, though nothing has changed in my setup
besides updating Lyx and Latex via TexLive. I install the embrac package,
which ensures non-italic brackets in otherwise italicized environments. This
used to work without a problem, but now generates the error message:
LaTeX3 Error: Command '\textsi' not yet defined!
I am sure of my trouble-shooting, since commenting out the usepackage command
eliminates the error.
When I was using Lyx a year ago, I wasn't seeing any mentions of LaTex3, I'm
fairly sure (and no errors from embrac). Any idea what's going wrong and how I
can eliminate the problem or work around it?
David,
Additional details will be useful to folks if they wish to help. For example,
what versions of LyX and TeXLive were being used "before" and "after"? What
version of macOS were you using before and after? Perhaps most important:
please provide a minimal working example (MWE)
[https://wiki.lyx.org/FAQ/MinimalExample] that demonstrates the problem now
(and, ideally, that used to work before).
Regards,
Joel
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: "LaTeX3 Error: Command '\textsi' not yet defined!"
One final note: I have discovered that if I go to TexLive and change Configure > Change Default Tex Live Version from "TeXLive-2019" to "TeXLive-2018", the error and the "L3 Programming Layer" messages disappear. I hope that narrows things down sufficiently. -David On Feb 16, 2020, at 11:49 AM, David Pesetsky mailto:pese...@mit.edu>> wrote: Before (June 2019, via MacOS Time Machine): LyX 2.3.2 TexLive 1.35 MacOS Mojave (10.14.x) Now Lyx 2.3.4.2 TexLive 1.36 MacOS Catalina (10.15.3) Minimal Working Example: without embrac package: with embrac package: Without embrac, the file compiles successfully, but does display "L3 Programming Layer " while compiling (as does every Lyx file at the moment). Hope this gives you what you need to help, and many thanks in advance. -David On Feb 15, 2020, at 11:24 PM, Joel Kulesza mailto:jkule...@gmail.com>> wrote: On Sat, Feb 15, 2020 at 3:53 PM David Pesetsky mailto:pese...@mit.edu>> wrote: I was using Lyx for Mac rather extensively to write a long-ish manuscript about a year ago, but have been away from it for a while. In the interval, a problem has arisen, though nothing has changed in my setup besides updating Lyx and Latex via TexLive. I install the embrac package, which ensures non-italic brackets in otherwise italicized environments. This used to work without a problem, but now generates the error message: LaTeX3 Error: Command '\textsi' not yet defined! I am sure of my trouble-shooting, since commenting out the usepackage command eliminates the error. When I was using Lyx a year ago, I wasn't seeing any mentions of LaTex3, I'm fairly sure (and no errors from embrac). Any idea what's going wrong and how I can eliminate the problem or work around it? David, Additional details will be useful to folks if they wish to help. For example, what versions of LyX and TeXLive were being used "before" and "after"? What version of macOS were you using before and after? Perhaps most important: please provide a minimal working example (MWE) [https://wiki.lyx.org/FAQ/MinimalExample] that demonstrates the problem now (and, ideally, that used to work before). Regards, Joel -- David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>] Department of Linguistics and Philosophy 32-D862 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html -- David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>] Department of Linguistics and Philosophy 32-D862 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: "LaTeX3 Error: Command '\textsi' not yet defined!"
Before (June 2019, via MacOS Time Machine): LyX 2.3.2 TexLive 1.35 MacOS Mojave (10.14.x) Now Lyx 2.3.4.2 TexLive 1.36 MacOS Catalina (10.15.3) Minimal Working Example: without embrac package: newfile3.lyx Description: newfile3.lyx with embrac package: newfile3 produces error.lyx Description: newfile3 produces error.lyx Without embrac, the file compiles successfully, but does display "L3 Programming Layer " while compiling (as does every Lyx file at the moment).Hope this gives you what you need to help, and many thanks in advance. -DavidOn Feb 15, 2020, at 11:24 PM, Joel Kulesza <jkule...@gmail.com> wrote:On Sat, Feb 15, 2020 at 3:53 PM David Pesetsky <pese...@mit.edu> wrote: I was using Lyx for Mac rather extensively to write a long-ish manuscript about a year ago, but have been away from it for a while. In the interval, a problem has arisen, though nothing has changed in my setup besides updating Lyx and Latex via TexLive. I install the embrac package, which ensures non-italic brackets in otherwise italicized environments. This used to work without a problem, but now generates the error message: LaTeX3 Error: Command '\textsi' not yet defined! I am sure of my trouble-shooting, since commenting out the usepackage command eliminates the error. When I was using Lyx a year ago, I wasn't seeing any mentions of LaTex3, I'm fairly sure (and no errors from embrac). Any idea what's going wrong and how I can eliminate the problem or work around it?David,Additional details will be useful to folks if they wish to help. For example, what versions of LyX and TeXLive were being used "before" and "after"? What version of macOS were you using before and after? Perhaps most important: please provide a minimal working example (MWE) [https://wiki.lyx.org/FAQ/MinimalExample] that demonstrates the problem now (and, ideally, that used to work before).Regards,Joel -- David Pesetsky [pese...@mit.edu]Department of Linguistics and Philosophy32-D862 Massachusetts Institute of Technology77 Massachusetts AvenueCambridge, MA 02139 USA(617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: "LaTeX3 Error: Command '\textsi' not yet defined!"
Thanks. Is there a way to stop LaTeX3 from compiling the file? In fact, independent of using or not using this package, since starting to use Lyx again a day ago, no matter what I compile, I periodically see the message "L3 Programming Layer " on the status bar at the bottom of the Lyx window. Lyx 2.3.4.2 MacOS Catalina 10.15.3 -David On Feb 16, 2020, at 6:34 AM, Richard Kimberly Heck mailto:rikih...@lyx.org>> wrote: On 2/15/20 5:52 PM, David Pesetsky wrote: I was using Lyx for Mac rather extensively to write a long-ish manuscript about a year ago, but have been away from it for a while. In the interval, a problem has arisen, though nothing has changed in my setup besides updating Lyx and Latex via TexLive. I install the embrac package, which ensures non-italic brackets in otherwise italicized environments. This used to work without a problem, but now generates the error message: LaTeX3 Error: Command '\textsi' not yet defined! I am sure of my trouble-shooting, since commenting out the usepackage command eliminates the error. This is pretty suspicious. It suggests, to me, that LaTeX3 is being used to compile this file, which will almost certainly cause major problems with LyX. Then again, it's possible that the problem is just local to the embrac package. You might try writing the maintainer at cont...@mychemistry.eu<mailto:cont...@mychemistry.eu>. Riki -- David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>] Department of Linguistics and Philosophy 32-D862 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
"LaTeX3 Error: Command '\textsi' not yet defined!"
I was using Lyx for Mac rather extensively to write a long-ish manuscript about a year ago, but have been away from it for a while. In the interval, a problem has arisen, though nothing has changed in my setup besides updating Lyx and Latex via TexLive. I install the embrac package, which ensures non-italic brackets in otherwise italicized environments. This used to work without a problem, but now generates the error message: LaTeX3 Error: Command '\textsi' not yet defined! I am sure of my trouble-shooting, since commenting out the usepackage command eliminates the error. When I was using Lyx a year ago, I wasn't seeing any mentions of LaTex3, I'm fairly sure (and no errors from embrac). Any idea what's going wrong and how I can eliminate the problem or work around it? Thanks, David -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: subscripts and superscripts display problem
Thanks — reported. > On Jul 8, 2018, at 8:00 PM, Richard Kimberly Heck wrote: > > On 07/08/2018 03:42 PM, Joel Kulesza wrote: >> >> On Jul 8, 2018, at 10:49, David Pesetsky > <mailto:pese...@mit.edu>> wrote: >> >>> And an update: I've discovered the problem previously reported here >>> (missed this for some reason when searching earlier): >>> >>> https://tex.stackexchange.com/questions/311041/subscript-and-superscript-in-lyx-leave-large-gaps-in-onscreen-editor >>> >>> <https://tex.stackexchange.com/questions/311041/subscript-and-superscript-in-lyx-leave-large-gaps-in-onscreen-editor> >>> >>> -- with a reference to this bug report: >>> https://www.lyx.org/trac/ticket/10177 >>> <https://www.lyx.org/trac/ticket/10177> >>> >>> Is there an approved way to add my own "please fix this" to that bug report >>> from two years ago? >> >> I’m not sure of it’s acceptability, but if I find an unresolved bug that I’m >> also afflicted by, I comment with the specifics (LyX version, OS, etc.) to >> (a) provide additional information about extent of effect, (b) indicate >> interest, and (c) get CC’d on any replies so I can follow and/or help debug >> as the issue is addressed by the dev team. > > More info about such bugs is always welcome. And if more people seem to be > affected, then that does tend to bring attention to the issue. > > Riki > - smime.p7s Description: S/MIME cryptographic signature
Re: subscripts and superscripts display problem
And an update: I've discovered the problem previously reported here (missed
this for some reason when searching earlier):
https://tex.stackexchange.com/questions/311041/subscript-and-superscript-in-lyx-leave-large-gaps-in-onscreen-editor
<https://tex.stackexchange.com/questions/311041/subscript-and-superscript-in-lyx-leave-large-gaps-in-onscreen-editor>
-- with a reference to this bug report: https://www.lyx.org/trac/ticket/10177
<https://www.lyx.org/trac/ticket/10177>
Is there an approved way to add my own "please fix this" to that bug report
from two years ago?
-David
> On Jul 8, 2018, at 12:42 PM, David Pesetsky wrote:
>
> OK, thank you. I've pinpointed the issue now.
>
> Early in using Lyx a year or so ago, I was othered by the absence of
> on-screen margins, the text running right up to the edge of the window in the
> default configuration. Somewhere online, I found the advice to modify "Local
> Layout" under Document>Settings to take care of this. Following what I had
> read, I added to Local Layout the following:
>
> Format 60
> RightMargin 10pt
> LeftMargin 10pt
>
> — which did the trick, as far as I was concerned.
>
> What I have now learned is that my LeftMargin setting is responsible for what
> I now assume is a bug in the display of superscripts and subscripts. When I
> remove this line, the problem disappears (along with my onscreen left
> margin). When I put it back, the problem reappears. The other two commands
> that I added to Local Layout have no effect on this problem.
>
> Unless this is a feature rather than a bug, for some reason, I assume this is
> something to report, but perhaps you will know better than me how to report
> it informatively?
>
> For now, I will live with my onscreen margins and the (presumed) bug, unless
> you have a better suggestion. Thank you again.
>
> -David
>
>
>> On Jul 8, 2018, at 12:10 PM, Joel Kulesza > <mailto:jkule...@gmail.com>> wrote:
>>
>> On Sun, Jul 8, 2018 at 9:52 AM, David Pesetsky > <mailto:pese...@mit.edu>> wrote:
>> -
>>
>>> On Jul 8, 2018, at 11:48 AM, Joel Kulesza >> <mailto:jkule...@gmail.com>> wrote:
>>>
>>> On Sun, Jul 8, 2018 at 9:29 AM, David Pesetsky >> <mailto:pese...@mit.edu>> wrote:
>>> When I add text as a subscript or superscript using
>>> Insert>Formatting>{Sub,Super}script, Lyx 2.3.0 adds a large onscreen
>>> horizontal gap before the text. This appears to be WYSIWYG problem only,
>>> as the Latex output does not have this problem (and there is no gap, as far
>>> as the onscreen cursor is concerned). I don't see anything about this in
>>> the bug tracker, so is it something I should file as a bug? Or something I
>>> did, without knowing it ...?
>>>
>>> -David
>>>
>>> I don't see similar behavior with LyX 2.3.0 on OS X 10.13.5 (see attached
>>> for what I see).
>>>
>>> It looks like your LyX background color is different from the default
>>> (white rather than the default beige). Perhaps another customization is
>>> driving this behavior?
>>
>> Right, that's what I was wondering, but I can't think of what. I changed
>> some colors a while ago, and picked an onscreen font — but I've tried
>> tinkering with different onscreen fonts, with no difference in the
>> superscript/subscript problem.
>>
>> What I would do to diagnose this:
>>
>> Rename ~/Library/Application Support/LyX-2.3 to ~/Library/Application
>> Support/LyX-2.3.bak
>>
>> Relaunch LyX 2.3.0. It will think it's a new installation with no
>> configuration files and will generate them (taking longer than usual to
>> start while doing so). Run a test to see if the sub/superscripts are
>> "normal." If so, it is something in the non-default settings. From there,
>> you can compare the contents of the new (clean) configuration files in that
>> directory to the backup you made.
>>
>> To recover your old settings, for better or worse, remove the "new"
>> ~/Library/Application Support/LyX-2.3 directory and copy over the "old",
>> backed-up, one from ~/Library/Application Support/LyX-2.3.bak.
>>
>> - Joel
>>
>>
>
> --
> David Pesetsky[pese...@mit.edu <mailto:pese...@mit.edu>]
> Department of Linguistics and Philosophy
> 32-D818 Massachusetts Institute of Technology
> 77 Massachusetts Avenue
> Cambridge, MA 02139 USA
> (617) 253-0957 office (617) 253-5017 fax
> http://web.mit.edu/linguistics/www/pesetsky.home.html
> <http://web.mit.edu/linguistics/www/pesetsky.home.html>
--
David Pesetsky [pese...@mit.edu]
Department of Linguistics and Philosophy
32-D818 Massachusetts Institute of Technology
77 Massachusetts Avenue
Cambridge, MA 02139 USA
(617) 253-0957 office (617) 253-5017 fax
http://web.mit.edu/linguistics/www/pesetsky.home.html
smime.p7s
Description: S/MIME cryptographic signature
Re: subscripts and superscripts display problem
OK, thank you. I've pinpointed the issue now.
Early in using Lyx a year or so ago, I was othered by the absence of on-screen
margins, the text running right up to the edge of the window in the default
configuration. Somewhere online, I found the advice to modify "Local Layout"
under Document>Settings to take care of this. Following what I had read, I
added to Local Layout the following:
Format 60
RightMargin 10pt
LeftMargin 10pt
— which did the trick, as far as I was concerned.
What I have now learned is that my LeftMargin setting is responsible for what I
now assume is a bug in the display of superscripts and subscripts. When I
remove this line, the problem disappears (along with my onscreen left margin).
When I put it back, the problem reappears. The other two commands that I added
to Local Layout have no effect on this problem.
Unless this is a feature rather than a bug, for some reason, I assume this is
something to report, but perhaps you will know better than me how to report it
informatively?
For now, I will live with my onscreen margins and the (presumed) bug, unless
you have a better suggestion. Thank you again.
-David
> On Jul 8, 2018, at 12:10 PM, Joel Kulesza wrote:
>
> On Sun, Jul 8, 2018 at 9:52 AM, David Pesetsky <mailto:pese...@mit.edu>> wrote:
> -
>
>> On Jul 8, 2018, at 11:48 AM, Joel Kulesza > <mailto:jkule...@gmail.com>> wrote:
>>
>> On Sun, Jul 8, 2018 at 9:29 AM, David Pesetsky > <mailto:pese...@mit.edu>> wrote:
>> When I add text as a subscript or superscript using
>> Insert>Formatting>{Sub,Super}script, Lyx 2.3.0 adds a large onscreen
>> horizontal gap before the text. This appears to be WYSIWYG problem only, as
>> the Latex output does not have this problem (and there is no gap, as far as
>> the onscreen cursor is concerned). I don't see anything about this in the
>> bug tracker, so is it something I should file as a bug? Or something I did,
>> without knowing it ...?
>>
>> -David
>>
>> I don't see similar behavior with LyX 2.3.0 on OS X 10.13.5 (see attached
>> for what I see).
>>
>> It looks like your LyX background color is different from the default (white
>> rather than the default beige). Perhaps another customization is driving
>> this behavior?
>
> Right, that's what I was wondering, but I can't think of what. I changed
> some colors a while ago, and picked an onscreen font — but I've tried
> tinkering with different onscreen fonts, with no difference in the
> superscript/subscript problem.
>
> What I would do to diagnose this:
>
> Rename ~/Library/Application Support/LyX-2.3 to ~/Library/Application
> Support/LyX-2.3.bak
>
> Relaunch LyX 2.3.0. It will think it's a new installation with no
> configuration files and will generate them (taking longer than usual to start
> while doing so). Run a test to see if the sub/superscripts are "normal." If
> so, it is something in the non-default settings. From there, you can compare
> the contents of the new (clean) configuration files in that directory to the
> backup you made.
>
> To recover your old settings, for better or worse, remove the "new"
> ~/Library/Application Support/LyX-2.3 directory and copy over the "old",
> backed-up, one from ~/Library/Application Support/LyX-2.3.bak.
>
> - Joel
>
>
--
David Pesetsky [pese...@mit.edu]
Department of Linguistics and Philosophy
32-D818 Massachusetts Institute of Technology
77 Massachusetts Avenue
Cambridge, MA 02139 USA
(617) 253-0957 office (617) 253-5017 fax
http://web.mit.edu/linguistics/www/pesetsky.home.html
smime.p7s
Description: S/MIME cryptographic signature
Re: subscripts and superscripts display problem
-
> On Jul 8, 2018, at 11:48 AM, Joel Kulesza wrote:
>
> On Sun, Jul 8, 2018 at 9:29 AM, David Pesetsky <mailto:pese...@mit.edu>> wrote:
> When I add text as a subscript or superscript using
> Insert>Formatting>{Sub,Super}script, Lyx 2.3.0 adds a large onscreen
> horizontal gap before the text. This appears to be WYSIWYG problem only, as
> the Latex output does not have this problem (and there is no gap, as far as
> the onscreen cursor is concerned). I don't see anything about this in the
> bug tracker, so is it something I should file as a bug? Or something I did,
> without knowing it ...?
>
> -David
>
> I don't see similar behavior with LyX 2.3.0 on OS X 10.13.5 (see attached for
> what I see).
>
> It looks like your LyX background color is different from the default (white
> rather than the default beige). Perhaps another customization is driving
> this behavior?
Right, that's what I was wondering, but I can't think of what. I changed some
colors a while ago, and picked an onscreen font — but I've tried tinkering with
different onscreen fonts, with no difference in the superscript/subscript
problem.
>
> - Joel
>
>
smime.p7s
Description: S/MIME cryptographic signature
subscripts and superscripts display problem
When I add text as a subscript or superscript using
Insert>Formatting>{Sub,Super}script, Lyx 2.3.0 adds a large onscreen
horizontal gap before the text. This appears to be WYSIWYG problem only, as
the Latex output does not have this problem (and there is no gap, as far as the
onscreen cursor is concerned). I posted a screenshot here:
https://imgur.com/a/FSnSRsP
I don't see anything about this in the bug tracker, so is it something I should
file as a bug? Or something I did, without knowing it ...?
-David
smime.p7s
Description: S/MIME cryptographic signature
feature request: text search in LaTex Preamble
I often find myself hunting for something in the preamble and having to cut and paste the contents of the "Document Settings/LaTex Preamble" window into a text processing program to search for what I want. (And then I sometimes tinker with it in the text processing program, forgetting that this does nothing until I go back to LyX and make the change there.) It would be nice to have a text search facility available within this LyX window, if possible. Or am I missing something and the feature is there somewhere? (If there is another place to post feature requests let me know. The bug tracker looks like it's only for bugs.) -David
Re: binding "Wrap by Preview" to a key
Excellent, that works — thank you so much! I added an additional char-forward to the end of your incantation, so I stay within the innermost box. -David > On Jan 17, 2018, at 2:05 PM, Paul A. Rubin <parubi...@gmail.com> wrote: > > On 01/17/2018 01:28 PM, David Pesetsky wrote: >> Is there any way to create a keyboard shortcut for “Wrap by Preview”, which >> otherwise appears only in the control-click/right-click contextual menu when >> clicking in an ERT box? >> >> I don’t see anything obvious in the list of keyboard shortcut possibilities >> offered in the preference settings — but perhaps I’m missing something? >> >> -David >> >> > You can try binding the following incantation to a keyboard shortcut of your > choosing: > > command-sequence repeat > 1;inset-toggle;char-forward;char-backward;char-forward-select;preview-insert;char-backward;char-backward;inset-toggle > > Paul > -- David Pesetsky [pese...@mit.edu] Head, Department of Linguistics and Philosophy 32-D818 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html
binding "Wrap by Preview" to a key
Is there any way to create a keyboard shortcut for “Wrap by Preview”, which otherwise appears only in the control-click/right-click contextual menu when clicking in an ERT box? I don’t see anything obvious in the list of keyboard shortcut possibilities offered in the preference settings — but perhaps I’m missing something? -David
Re: replace-all within selected text
I see — the discussion seems to have gotten a bit confused around eight years ago, but the discussion around three years ago hits the nail on the head. It should work this way in "replace all", and not in simple find or find-replace. I am not a member of the Lyx team, obviously, so not part of that discussion — but could you or someone revive the discussion on my behalf (as I see someone did for some other user)? Thanks! > On Aug 6, 2017, at 8:02 PM, Paul A. Rubin <parubi...@gmail.com> wrote: > > On 08/06/2017 06:52 PM, David Pesetsky wrote: >> I just learned the (very) hard way that Lyx, unlike standard word processors >> and other text-manipulating software that I've used, does not limit the >> effect of "replace all" to selected text (when something has been selected). >> >> Am I unaware of some switch that can change this behavior, perhaps — or is >> there really no way to to select some text and "replace all" limited to >> what's been selected? It's a feature I use constantly in other applications >> that's become second-nature ... >> >> -David > There's a feature request on file for this: > http://www.lyx.org/trac/ticket/2548. Looks as if the ticket hasn't been > updated in two years or so. > > Paul > -
replace-all within selected text
I just learned the (very) hard way that Lyx, unlike standard word processors and other text-manipulating software that I've used, does not limit the effect of "replace all" to selected text (when something has been selected). Am I unaware of some switch that can change this behavior, perhaps — or is there really no way to to select some text and "replace all" limited to what's been selected? It's a feature I use constantly in other applications that's become second-nature ... -David
Re: Is "Citation Style" menu tweakable?
Thanks for your continued help! I have solved the problem, with the help of
(the presuppositions of) your questions and this:
https://tex.stackexchange.com/questions/56525/natbib-setcitestyle-causes-undefined-control-sequence-error?rq=1.
Early in my exploring of Lyx a few weeks ago, I took advantage of the
information offered by Maria Gouskova, who is in my field, at
https://www.gouskova.com/resources/. That includes a link to her texmf
directory with field-specific stuff in it, with an invitation to copy that into
one's own texmf directory, which I did. That turns out to have included an
out-of-date version of natbib.sty, which was the cause of my error messsages.
Removing it solved the problem.
Thanks again,
David
On Jun 20, 2017, at 11:23 PM, Richard Heck
<rgh...@lyx.org<mailto:rgh...@lyx.org>> wrote:
On 06/20/2017 06:25 PM, David Pesetsky wrote:
Thank you for your detailed reply (and hello)! Your suggestion to add "comma"
to [...]Class Options>Custom works very well, thank you!
But no matter what I put after \setcitestyle (or where I locate the command in
the document -- preamble, body), I get an error message from Lyx — for example:
\setcitestyle
{notesep={: }}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
It's not worth chasing down this problem to the ends of the earth, but if you
have any troubleshooting suggestions, I'd be happy to try them.
Very odd. The \setcitestyle command is defined by natbib.sty, and you said you
were using natbib, yes? (It did not exist before version 8 of natbib, but that
was about a decade ago.) What OS are you using? Do you know what LaTeX
distribution you have? Actually, maybe a better questin is: What document class
are you using?
If you could produce as small a file as possible that causes this to happen and
post that, then it will help debug the issue.
Richard
--
David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>]
Head, Department of Linguistics and Philosophy
32-D818 Massachusetts Institute of Technology
77 Massachusetts Avenue
Cambridge, MA 02139 USA
(617) 253-0957 office (617) 253-5017 fax
http://web.mit.edu/linguistics/www/pesetsky.home.html
Re: Is "Citation Style" menu tweakable?
Thank you for your detailed reply (and hello)! Your suggestion to add "comma"
to [...]Class Options>Custom works very well, thank you!
But no matter what I put after \setcitestyle (or where I locate the command in
the document -- preamble, body), I get an error message from Lyx — for example:
\setcitestyle
{notesep={: }}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
It's not worth chasing down this problem to the ends of the earth, but if you
have any troubleshooting suggestions, I'd be happy to try them.
Thank you again!
-David
On Jun 19, 2017, at 10:45 PM, Richard Heck
<rgh...@lyx.org<mailto:rgh...@lyx.org>> wrote:
On 06/19/2017 08:48 PM, David Pesetsky wrote:
Is there a way to tweak Lyx so the Citation dialog shows a different set of
options for "Citation Style" than the ones that appear by default when I have
selected "natbib" and "author-year" in Document Settings/Bibliography? I'd be
interested in having a comma rather than semicolon separating multiple
references, for example.
There's nothing I can't produce manually, of course, by simply selecting the
date-only option on the Citation Style pull-down menu and typing what I want
before and after the date, but if I could take advantage of the pull-down menu
options more often, it would save some effort.
Similarly, for some purposes, at least, I'd be happy if I could tweak "text
after" in the same dialog so that it ends up preceded by a colon rather than
the comma that Lyx inserts.
The issues you're raising here are actually LaTeX issues, rather than
LyX issues. It's important, in understanding how LyX operates, to
separate these: There's the question how things look in LyX; then there
is the question how the PDF looks when it is generated. The latter
ultimately concerns LaTeX. In some cases, LyX provides a 'native' way to
tweak the LaTeX output. But oftentimes, you have to do something
manually, e.g., add something to the LaTeX preamble.
In this case, the semi-colon citation-separator and comma before the
"text after" are being inserted by natbib, which is what formats the
citations and bibliogrpahy. So it's natbib that we need to control. The
natbib manual
http://mirror.utexas.edu/ctan/macros/latex/contrib/natbib/natbib.pdf
has a bunch of information about tweaks. Section 5 of the manual
mentions a number of package options that change global behavior. The
one you want for your first request is "comma". You just add this, as a
class option, under Document> Settings> Class Options> Custom. (If there
already are some there, this is a comma-separated list, so add it with a
new comma, e.g.: draft,comma.)
For the other one, section 2.9 of the natbib manual explains how to
select citation punctuation using the \setcitestyle command. In your
case, you want:
\setcitestyle{notesep={: }}
to select a colon followed by a space. It is probably easiest to put
this command into Document> Settings> LaTeX Preamble, though it can also
be entered as TeX code in the document itself. Note, by the way, that
natbib seems to be quite picky about space before and after the "=",
i.e., it does not like space there.
As it happens, \setcitestyle will also control the citation separator,
so you could just do:
\setcitestyle{notesep = {: },citesep={,}}
and skip the class option, if you wanted.
Note that this will NOT change how the citations appear within LyX
itself. That can be done, but it's a much messier matter.
Richard Heck
PS Yes, the Richard Heck from the other side of L
--
David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>]
Head, Department of Linguistics and Philosophy
32-D818 Massachusetts Institute of Technology
77 Massachusetts Avenue
Cambridge, MA 02139 USA
(617) 253-0957 office (617) 253-5017 fax
http://web.mit.edu/linguistics/www/pesetsky.home.html
Is "Citation Style" menu tweakable?
Is there a way to tweak Lyx so the Citation dialog shows a different set of options for "Citation Style" than the ones that appear by default when I have selected "natbib" and "author-year" in Document Settings/Bibliography? I'd be interested in having a comma rather than semicolon separating multiple references, for example. There's nothing I can't produce manually, of course, by simply selecting the date-only option on the Citation Style pull-down menu and typing what I want before and after the date, but if I could take advantage of the pull-down menu options more often, it would save some effort. Similarly, for some purposes, at least, I'd be happy if I could tweak "text after" in the same dialog so that it ends up preceded by a colon rather than the comma that Lyx inserts. -David
Re: hide "BibTeX Generated Bibliography"?
Thanks! That is probably what I would have done if Jürgen had not made his suggestion, which allows me to use my normal key binding for getting to the end of the document (without wrong consequences in documents without bibliographies). -David > On Jun 10, 2017, at 11:57 AM, Paul A. Rubin <parubi...@gmail.com> wrote: > > On 06/10/2017 09:23 AM, David Pesetsky wrote: >> Is there any way to have BibTex citations resolve correctly while editing >> without having "BibTeX Generated Bibliography" constantly visible at the >> bottom of the buffer. I find myself constantly going to the end of the >> buffer to continue writing my document and having to hit the back arrow and >> return to avoid "BibTeX Generated Bibliography" — plus it's distracting. >> If there's a way to hide it, or to get Lyx to resolve citations on-screen >> and in pdf previews without it, that would be excellent. >> >> (I am new to Lyx, so if the answer is obvious, or somewhere in the >> documentation that I missed, my apologies.) >> >> -David >> > Besides Jürgen's suggestion, another possibility is to bind the following to > a key combination of your choosing: > > command-sequence buffer-end; char-left; paragraph-break; > > This does what you've been doing manually -- jump to the end of the document > (presumably after the bibliography inset), back up one character (presumably > to just before the inset) and start a new paragraph. > > Paul >
Re: hide "BibTeX Generated Bibliography"?
The two suggestions together appear to do exactly what I need — many thanks!
-David
> On Jun 10, 2017, at 9:39 AM, Jürgen Spitzmüller <sp...@lyx.org> wrote:
>
> Am Samstag, den 10.06.2017, 13:23 +0000 schrieb David Pesetsky:
>> Is there any way to have BibTex citations resolve correctly while
>> editing without having "BibTeX Generated Bibliography" constantly
>> visible at the bottom of the buffer.
>
> With a hack, yes (see below).
>
>> I find myself constantly going to the end of the buffer to continue
>> writing my document and having to hit the back arrow and return to
>> avoid "BibTeX Generated Bibliography" — plus it's distracting. If
>> there's a way to hide it, or to get Lyx to resolve citations on-
>> screen and in pdf previews without it, that would be excellent.
>
> The inset is needed for two reasons: (1) it tells LaTeX where to put
> the references (they could be placed anywhere in the document) and (2)
> it tells LyX which database and and style is used.
>
> For the latter, it does not matter where you place the inset. So you
> could place it at the beginning of a document, but in a note inset (in
> order to prevent it being printed at this position).
>
> For the former, you could add to your preamble something such as:
>
> \AtEndDocument{%
> \bibliographystyle{}
> \bibliography{}
> }
>
> (i.e., the LaTeX output of the "BibTeX Generated Bibliography" inset
> wrapped into \AtEndDocument).
>
> HTH
> Jürgen
>
>>
>> (I am new to Lyx, so if the answer is obvious, or somewhere in the
>> documentation that I missed, my apologies.)
>>
>> -David
hide "BibTeX Generated Bibliography"?
Is there any way to have BibTex citations resolve correctly while editing without having "BibTeX Generated Bibliography" constantly visible at the bottom of the buffer. I find myself constantly going to the end of the buffer to continue writing my document and having to hit the back arrow and return to avoid "BibTeX Generated Bibliography" — plus it's distracting. If there's a way to hide it, or to get Lyx to resolve citations on-screen and in pdf previews without it, that would be excellent. (I am new to Lyx, so if the answer is obvious, or somewhere in the documentation that I missed, my apologies.) -David
Re: Lyx on Mac: Preferences problems
Yes indeed, it looks like this is fixed in 2.3(alpha). Many thanks, looking forward to its official release. -David Le 29/05/2017 à 15:26, David Pesetsky a écrit : Can you please confirm that it is fixed in 2.3(alpha)? Relevant commit is 881b7ec67 which was not backported to 2.2.3 as it was assumed to be minor. Guillaume
Re: Lyx on Mac: Preferences problems
No — no Karabiner on my system. -David > On May 29, 2017, at 4:28 PM, Scott Kostyshak <skost...@lyx.org> wrote: > > On Mon, May 29, 2017 at 05:41:16PM +, David Pesetsky wrote: >> Dear Anders and Joel, >> >> Thank you both. >> >> Just to add one more piece of data. To try to isolate what might cause Lyx >> to freeze for me but not for you, I booted in "safe mode", so my system >> would be running only the bare essentials. Lyx behaved exactly the same, >> with the same freeze. >> >> So though it sounds like the change in dialog focus that you are seeing >> might well be related to my more severe problem, I haven't a clue why we are >> seeing different behavior. Very puzzling. >> >> -David > > David, you don't happen to have a program "Karabiner" installed, do you? > Please check in the list of running applications to make sure (in the > past some have had it installed without knowing). > > Scott -- David Pesetsky [pese...@mit.edu] Head, Department of Linguistics and Philosophy 32-D818 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html
Re: Lyx on Mac: Preferences problems
Dear Anders and Joel, Thank you both. Just to add one more piece of data. To try to isolate what might cause Lyx to freeze for me but not for you, I booted in "safe mode", so my system would be running only the bare essentials. Lyx behaved exactly the same, with the same freeze. So though it sounds like the change in dialog focus that you are seeing might well be related to my more severe problem, I haven't a clue why we are seeing different behavior. Very puzzling. -David On May 29, 2017, at 1:13 PM, Anders Ekberg <a...@me.com<mailto:a...@me.com>> wrote: On 2017May29, at 18:45, Joel Kulesza <jkule...@gmail.com<mailto:jkule...@gmail.com>> wrote: On Mon, May 29, 2017 at 8:44 AM, David Pesetsky <pese...@mit.edu<mailto:pese...@mit.edu>> wrote: 1. Open a Lyx file in the editor window. 2. Change any setting, for example, Screen Font (but it can be anything, on any submenu 3. Click "Apply" 4. A white box appears and the program freezes. 5. Also: if you click on the editor window while the program is in its frozen state, that window turns black. Thanks for the detailed steps. Unfortunately, I cannot reproduce with LyX 2.2.3 on OS X 10.12.5. However, there is some differing behavior I experience which might explain why you see different things. When I do NOT have a document open, I can tweak a preference, Apply, Save, and all is well. This is also the behavior I'd expect relative to my next point. When I do have a document open, I can tweak a preference, Apply, *the dialog window goes to the background*, I retrieve the dialog, Save, and all is well. I wonder if someone can track down why the dialog focus changes depending on whether a document is open or not. Can’t track down why the dialog focus changes, but can confirm the behaviour that Apply with a document open sends the dialog window to the background (OSX 10.12.5 here too if that is any clue). /Anders
Re: Lyx on Mac: Preferences problems
Sending a second time, since evidently the version with attachments did not go through. On May 29, 2017, at 10:44 AM, David Pesetsky <pese...@mit.edu<mailto:pese...@mit.edu>> wrote: Thank you for your reply. This is Lyx version 2.2.3, installed from .dmg. Focusing on the first of the two problems I wrote about: 1. Open LyX:Preferences (with no file open) 2. Change any setting, for example, Screen Font (but it can be any change on any submenu) 3. Click "Apply" 4. Click "Save" 5. all is well - the preference is saved and works but: 1. Open a Lyx file in the editor window. 2. Change any setting, for example, Screen Font (but it can be anything, on any submenu 3. Click "Apply" 4. A white box appears and the program freezes. 5. Also: if you click on the editor window while the program is in its frozen state, that window turns black. I don't know if this message board will accept attachments, but I'll send screen shots, in case they get through. On May 29, 2017, at 10:29 AM, Joel Kulesza <jkule...@gmail.com<mailto:jkule...@gmail.com>> wrote: On Mon, May 29, 2017 at 7:26 AM, David Pesetsky <pese...@mit.edu<mailto:pese...@mit.edu>> wrote: I have been trying out Lyx on the Mac over the past week, and have a repeated problem setting preferences. If I try to apply or save any preference from the Lyx menu while there is a document open, a blank white box appears (as if the system is trying to show me a message of some sort, except there is no message) and the program freezes. This is repeatable on both my laptop and iMac running MacOS 10.12.5, and the only way out is to force-quit the program. I eventually learned that setting preferences only works if there is no open document. Additionally, if I try to change a key binding that is already assigned to another function, the program notifies me, and asks me if I want to reassign the key — but if I say yes, I am dumped out of preferences and nothing is saved. These look like bugs, but any information or assistance (am I doing something wrong somewhere?) would be helpful. -David David: Which version of LyX (LyX Menu -> About LyX)? Installed from .dmg or compiled yourself? If you give a step-by-step examples to reproduce what you're experiencing, I'll try to reproduce and will report back. - Joel -- David Pesetsky [pese...@mit.edu<mailto:pese...@mit.edu>] Head, Department of Linguistics and Philosophy 32-D818 Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge, MA 02139 USA (617) 253-0957 office (617) 253-5017 fax http://web.mit.edu/linguistics/www/pesetsky.home.html
Lyx on Mac: Preferences problems
I have been trying out Lyx on the Mac over the past week, and have a repeated problem setting preferences. If I try to apply or save any preference from the Lyx menu while there is a document open, a blank white box appears (as if the system is trying to show me a message of some sort, except there is no message) and the program freezes. This is repeatable on both my laptop and iMac running MacOS 10.12.5, and the only way out is to force-quit the program. I eventually learned that setting preferences only works if there is no open document. Additionally, if I try to change a key binding that is already assigned to another function, the program notifies me, and asks me if I want to reassign the key — but if I say yes, I am dumped out of preferences and nothing is saved. These look like bugs, but any information or assistance (am I doing something wrong somewhere?) would be helpful. -David
