| 1 |
"Richard Fish" <bigfish@××××××××××.org> posted |
| 2 |
7573e9640611150103n45f56644s7d5dc92883323f2d@××××××××××.com, excerpted |
| 3 |
below, on Wed, 15 Nov 2006 02:03:49 -0700: |
| 4 |
|
| 5 |
> On 11/15/06, Richard Fish <bigfish@××××××××××.org> wrote: |
| 6 |
>> --deep ensures you get all of the very latest updates for everything. |
| 7 |
>> Well, /almost/ everything [1]. |
| 8 |
> |
| 9 |
> Hmm, forgot to explain [1]. |
| 10 |
|
| 11 |
Kinda obvious tip, but it's about all that works for me: Either always go |
| 12 |
to the bottom and immediately add the footnote when you do that, /then/ go |
| 13 |
back and finish your thought, or have a post-it note or something handy to |
| 14 |
tape to the edge of the monitor, or possibly over whether the post button |
| 15 |
is (if you don't use a keyboard shortcut), so you'll be sure to see it |
| 16 |
when you actually go to post. Moving a different window over the button |
| 17 |
may work as well, avoiding the necessity of those post-it notes. =8^) |
| 18 |
(Just don't do something that moves the window back behind the posting |
| 19 |
button again.) |
| 20 |
|
| 21 |
The same applies to mentioned attachments. =8^( I forget them /most/ of |
| 22 |
the time, unless I deal with them immediately or physically block my |
| 23 |
normal send method until they are attached. That's the /only/ two |
| 24 |
solutions I've found for what is otherwise a virtually hopeless case, in |
| 25 |
my case. =8^( |
| 26 |
|
| 27 |
-- |
| 28 |
Duncan - List replies preferred. No HTML msgs. |
| 29 |
"Every nonfree program has a lord, a master -- |
| 30 |
and if you use the program, he is your master." Richard Stallman |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-amd64@g.o mailing list |
Archives