How can I assign keyboard shortcuts to Clippings in BBEdit 9.2.1?
SemperFi
be called "Glossary" in BBEdit version 8.2.6 is now called
"Clippings." I also see that the bits of glossary text I created using
8.2.6 are still available to me under ...
~/Library/Application Support/BBEdit/Clippings/Universal Items
... which looks like what I had under 8.2.6 (except that "Clippings"
folder was called "Glossary," if I remember correctly).
In BBEdit 9.2.1, the Clippings menu > "Insert Clipping..." lets me
insert any of my existing Clippings at the current location of my
pointer. However, the keyboard shortcuts I created for my old Glossary
files are no longer operative. In fact, they're gone. When I examined
the BBEdit 9.2. User Manual to find out how to reinstate my keyboard
shortcuts, page 291 of that manual said,
"Assigning Key Equivalents to Clippings
"1 Select the clipping in the Clippings window.
"2 Click the Set Key button to display the Set Key sheet.
"3 Type the key equivalent. [...]
"4. Click Set."
Indeed, that's how it used to be under 8.2.6. But in 9.2.1 this vital
menu sheet seems to be missing.
Where did that Set Key menu sheet go? I don't seem to have one. I sure
would like to be able to reinstate (or redefine) keyboard shortcuts
for my Clippings to regain the speediest use of this BBEdit function.
klan...@gmail.com
>Yesterday I upgraded to BBEdit version 9.2.1. I see that what used to
>be called "Glossary" in BBEdit version 8.2.6 is now called
>"Clippings." I also see that the bits of glossary text I created using
>8.2.6 are still available to me under ...
>
[snip]
>Where did that Set Key menu sheet go? I don't seem to have one. I sure
>would like to be able to reinstate (or redefine) keyboard shortcuts
>for my Clippings to regain the speediest use of this BBEdit function.
For menu items, keyboard equivalents are set under Preferences
-> Menus.
For clippings, see the Set Key button at top right of the
clippings palettes.
Ken
--
Simple Lives Web Design
http://simplelives.com
Semper Fidelis
overlooked the Window > Palettes > Clippings portion. I guess I
thought everything having to do with Clippings would be found under
Clippings. My bad.
Thanks for setting me straight.
John Delacour
With varying frequency I copy text from a browser and paste it into a
BBEdit document. If I leave BBEdit idle for too long, it takes
several seconds for the application to reawake and these dalys add up
to an annoyance.
Is there a setting that will prevent BBEdit from dozing off?
JD
Bill Rowe
I rather doubt this is a BBEdit issue. I suggest looking at your
system preferences for disk/computer sleep. That is see if
unchecking the Put the hard disks to sleep when possible and
setting the computer sleep to never in the Energy Saver
preference pane doesn't fix things for you.
Jan Erik Moström
My guess is that has nothing to do with BBEdit but rather with
OS X. It probably swap out processes that haven't been used in a
while and then need to bring it back into memory before being
able to use it.
A typical example for is if I use Aperture and import new
images, this seem to require a lot of memory so OS X swap out
almost all other running processes and when I need to do
something it takes a huge amount of time before they become
active again.
jem
--
Jan Erik Moström, http://mostrom.eu
Bucky Junior
On Sep 21, 2009, at 7:04 AM, Jan Erik Moström wrote:
>
> On 09-09-20 at 23.08, John Delacour <johnde...@gmail.com> wrote:
>
>> With varying frequency I copy text from a browser and paste it
>> into a BBEdit document. If I leave BBEdit idle for too long,
>> it takes several seconds for the application to reawake and
>> these dalys add up to an annoyance.
>>
>> Is there a setting that will prevent BBEdit from dozing off?
>
> My guess is that has nothing to do with BBEdit but rather with
> OS X. It probably swap out processes that haven't been used in a
> while and then need to bring it back into memory before being
> able to use it.
Which to me sounds like a memory issue. The same thing happens when I
have 3-4 graphics programs running, three browsers with a dozen tabs
each, a virtual machine or two running and switch between programs.
Not BBEdit. Not a sleep issue. Not the OS as such, but how memory is
used allocated and, yes, swapped in and out. If you run top in a
terminal window and expose the top section where you can see the swaps
in and out. I'm sure if you read the man file for top, you could
figure out how to extract just that information. You'll probably find
that your memory is being swapped in and out.
Bucky
Bucky Junior
If you run top in a terminal window...
Try this top command
top -ovsize -Uusername -Frt -n15
top = command
-ovsize = order by virtual size
-Uusername = your user name
-Frt = don't calculate frameworks, report object memory map, translate usernames
-n15 = number of lines in report
You'll see at the end of the topmost section ### pageins and ### pageouts. Pageins are writing to disk-based swap file. Pageouts and reading from that swap file. Lots of pageouts relative to pageins means that you've used up your physical RAM and performance is degraded.
E.g., I have 5GB of RAM and have 13 visible applications running. I've got nearly 2 million pageins and 34 pageouts. Right now, my performance is quite acceptable.
For more information, this thread may explain better than I. <http://macosx.com/forums/mac-os-x-system-mac-software/47648-page-ins-page-outs-could-somebody-please-explain-me-idiot-fashion.html>
Bucky
Lewis@Gmail
wrote:
> top -ovsize -Uusername -Frt -n15
What version of top? On my 10.6 machine top does not like -Frt
Bucky Junior
but deleting the -Frt from the command line still gives the important
pageins/pageouts.
Be sure to substitute _your_ username in -Uusername. I copied back
from the message and (duh!) got invalid username.
Without the -Frt, and running an extremely RAM intensive flight
simulation program a while ago, this is the top section of the running
report. My pageouts are less than 3% of my pageins.
Processes: 98 total, 5 running, 5 stuck, 88 sleeping... 519
threads 11:20:39
Load Avg: 0.43, 0.39, 0.44 CPU usage: 3.60% user, 6.99% sys,
89.41% idle
SharedLibs: num = 8, resident = 59M code, 624K data, 4564K
linkedit.
MemRegions: num = 32678, resident = 1680M + 36M private, 493M shared.
PhysMem: 685M wired, 1627M active, 1450M inactive, 3760M used, 1360M
free.
VM: 17G + 377M 1788548(0) pageins, 53842(0) pageouts
More RAM is always good. As much as you can afford.