Am 21.02.2021 um 07:12 schrieb Daniel :
>
> On 2021-02-21 02:12, David Pesetsky wrote:
>> Perhaps there is a font size problem? This is what I see. Notice that not
>> only are the "<" and ">" indicators missing, but "Case sensitive" overlaps
>> the next checkbox. (Hoping this listserv
On 2021-02-21 02:12, David Pesetsky wrote:
Perhaps there is a font size problem? This is what I see. Notice that
not only are the "<" and ">" indicators missing, but "Case sensitive"
overlaps the next checkbox. (Hoping this listserv doesn't strip out
graphics attachments.)
I see the
'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
!
>
> 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
ilto: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
As I posted, I get the same, and I most certainly did all the
steps, it did find the string in thw window and with the "Find-Next" but
not with CMD-G
frontends/qt4/GuiApplication.cpp (1603): cmd: action: 241 [word-find]
arg: 'ermany
0 0 1' x: 0 y: 0
BufferView
Statusbar shows nothing.
/Applications/LyX.app/Contents/MacOS/lyx -dbg action
shows
frontends/qt4/GuiApplication.cpp (1603): cmd: action: 169
[word-find-forward] arg: '' x: 0 y: 0
BufferView.cpp (1261): BufferView::dispatch: cmd: action: 169
[word-find-forward] arg:
s?
>
> 1. Ctrl-F
> 2. Enter search string
> 3. Hit Enter to find first occurrence
> 4. Click into workarea OR close dialog
> 5. Hit ⌘-G to find next occurrences
>
> Jürgen
>
>
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Am Samstag, dem 13.02.2021 um 18:08 +0100 schrieb Daniel:
> frontends/qt4/GuiApplication.cpp (1603): cmd: action: 169
> [word-find-forward] arg: '' x: 0 y: 0
This indicates that there is no search string in the cache. Did you
really do step 3 in my recipe?
Jürgen
signature.asc
Description:
te:
>>
>> 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, i
On 2021-02-13 17:50, Jürgen Spitzmüller wrote:
Am Samstag, dem 13.02.2021 um 17:43 +0100 schrieb Daniel:
Seems not to work here either.
What does the statusbar show if you hit ⌘-G? Also, can you check for
"action" dbg messages?
Jürgen
No status bar message. When I select "action" in the
Am Samstag, dem 13.02.2021 um 17:43 +0100 schrieb Daniel:
> Seems not to work here either.
What does the statusbar show if you hit ⌘-G? Also, can you check for
"action" dbg messages?
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-users mailing list
dialog
5. Hit ⌘-G to find next occurrences
Jürgen
Seems not to work here either.
Daniel
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Am Samstag, dem 13.02.2021 um 18:03 +0200 schrieb Dr Eberhard W Lisse:
> Makes no difference here.
Just to be sure, did you really try this?
1. Ctrl-F
2. Enter search string
3. Hit Enter to find first occurrence
4. Click into workarea OR close dialog
5. Hit ⌘-G to find next occurrences
Jür
pparent 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'
rote:
>>
>> 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.
>>>
On Fri, Feb 12, 2021 at 8:24 AM David Pesetsky wrote:
> Pleased indeed, thank you!!!
>
> On Feb 12, 2021, at 10:14 AM, Jürgen Spitzmüller wrote:
>
> Am Freitag, dem 12.02.2021 um 14:53 + schrieb David Pesetsky:
>
> If you click on the document window, the "find
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
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, nothi
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 i
> On Feb 11, 2021, at 5:28 PM, David Pesetsky wrote:
>
> 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
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
signature.asc
Description: This is a digitally signed message part
--
lyx-users mailing list
lyx-users@lists.lyx.org
http:
I can also confirm that CMD-G is bound to word-find-forward in
2.3.6.2 and (that non working of if) has been irritating me on
all of my Macs for at least 5 but maybe even 10 years.
Does one of the (Core-) Developers have a Mac?
el
On 2021-02-12 04:39 , Richard Kimberly Heck wrote:
> On
On 2/11/21 9:38 PM, Richard Kimberly Heck wrote:
> On 2/11/21 8:21 PM, Paul A. Rubin wrote:
>> On 2/11/21 7:28 PM, David Pesetsky wrote:
>>> My Macintosh-educated fingers are used to ⌘-G for "find next" (used
>>> after using ⌘-F for "find"). Do
On 2/11/21 8:21 PM, Paul A. Rubin wrote:
> On 2/11/21 7:28 PM, David Pesetsky wrote:
>> 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 duplic
On 2/11/21 7:28 PM, David Pesetsky wrote:
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 c
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 — b
It would appear that on Sep 2, Scott Kostyshak did say:
> On Fri, Sep 02, 2016 at 09:52:13PM -0400, Joe Philbrook wrote:
> >
> > Ticket #10357 (new enhancement)
> >
> > How did I do?
>
> Looks good! I removed the keywords since we use a fixed set, which is
> described here:
>
On Fri, Sep 02, 2016 at 09:52:13PM -0400, Joe Philbrook wrote:
>
> It would appear that on Aug 31, Scott Kostyshak did say:
>
> > On Wed, Aug 31, 2016 at 07:39:34PM -0400, Joe Philbrook wrote:
> >
> > > Please tell me that I'm not looking at (3 x 3 = 9) nine trac tickets
> > > here...
> >
> >
It would appear that on Aug 31, Scott Kostyshak did say:
> On Wed, Aug 31, 2016 at 07:39:34PM -0400, Joe Philbrook wrote:
>
> > Please tell me that I'm not looking at (3 x 3 = 9) nine trac tickets here...
>
> Good point. I don't have general advice on what topics should be
> grouped. If they
On Wed, Aug 31, 2016 at 07:39:34PM -0400, Joe Philbrook wrote:
> Please tell me that I'm not looking at (3 x 3 = 9) nine trac tickets here...
Good point. I don't have general advice on what topics should be
grouped. If they are topics that shoudl be addressed all at once and it
would be silly to
uot;} That I may want
> > to Ignore. Or perhaps I wanted to use an unusual word such as hisself
> > instead of himself
> > because it's "In character" for the character being quoted and wish to aDd
> > it to my word list.
> > And while I never use it, the sa
oh"} That I may want
> to Ignore. Or perhaps I wanted to use an unusual word such as hisself instead
> of himself
> because it's "In character" for the character being quoted and wish to aDd it
> to my word list.
> And while I never use it, the same problem exists
it, the same problem exists for the "Find next" button.
Lately my problems with mouse operation have been getting worse:
It can take me over a minute to maneuver the "dag nabbed" rodent pointing
device over the correct
"durned" button... And the button keybindings ind
34 matches
Mail list logo
