I find it convenient to type Ctl-F and then enter some text to find it. If I click the “Next” button, the find dialog stays up, but if I hit the “return” key, it does not.
Any way to keep the dialog box up (as in the Windows version)?
I find it convenient to type Ctl-F and then enter some text to find it. If I click the “Next” button, the find dialog stays up, but if I hit the “return” key, it does not.
Any way to keep the dialog box up (as in the Windows version)?
Haven’t tried but remembered reading about it:
viewtopic.php?p=265280#p265280
EDIT––a few moments ago, I used the terminal command* in the first code box in that thread. It worked in macOS 10.12.6. (Thank you, KB.)
*replace “your_user_name” in the command (while maintaining the spacing) with your macOS user acct. name
If you don’t want to change the default preferences using scshrugged’s suggestion, then it may be worth knowing that cmd-g will still go to the next match (and cmd-shift-g the previous) even if the dialogue box is no longer visible.
Either:
Use CMD F to open find.
Type the word you are looking for.
Then use CMD G (as often as you want) to find the word you typed. The find dialogue will remain open and visible.
or:
A. Use CMD F to open find.
B. Type the word you are looking for.
C. Press ENTER to find the word you typed. The find dialogue will close, but the find function will remain available using CMD G. This method frees up screen space.
or:
I. Use CMD F to open find.
II. Type the word you are looking for.
III. Use the mouse or trackpad to tap on NEXT to find the word you typed. The find dialogue will remain open and visible.
Find Shortcuts
Find > CMD F
Find next > CMD G
Find previous > CMD SHIFT G
Find using the selected text > CMD E (then press CMD G to find the next instance of that word)
Slàinte mhòr.
Excellent.
Being a Mac newbie …
I decided to edit the plist. I opened com.literatureandlatte.scrivener3.plist with TextEdit.app, but it doesn’t look quite right. Also, I didn’t find a entry. Do I need a different editor?
Thanks.
You’re welcome. Although I’m not as much of a newbie as you, I’m far from seasoned. However you decide to proceed, stick to fundamentals. Double check your thinking and actions, and always have multiple backups to prepare for the unexpected.
As you found out,TextEdit doesn’t properly read binary format.
You’d need to convert the file to xml before editing then change it back after. A primer––in Terminal.app, to see the BSD General Commands Manual entry for property list utility enter:
man plutil
Or, do as KB says in steps #1-5 and use a different text editor. Note––TextWrangler has been sunsetted and supposedly isn’t compatible with macOS 10.13, and in step #3, KB certainly meant to write BBEdit rather than BBCode.
viewtopic.php?p=265356#p265356
TextWrangler/BBEdit at Bare Bones Software:
barebones.com/products/textwrangler/