The first GNHLUG meeting of 2007 was hosted by the Dartmouth-Lake
Sunapee Linux User Group as an informal dinner and chat at the Salt
Hill Pub adjacent to Colburn Park in the center of Lebanon. A good
time was had by all. Discussions were freeform and far-ranging,
including Google job
On 1/5/07, Bill McGonigle [EMAIL PROTECTED] wrote:
Here's a strange job control problem. I don't understand what the
root cause was. The original command was:
sudo emacs -nw /etc/yum.repos.d/rpmforge.repo
Everyone else already explained what is going on, and better than I
could have. I
Ben Scott [EMAIL PROTECTED] writes:
Everyone else already explained what is going on, and better than I
could have. I do have one question, though. Why does it work for me?
$ sudo emacs -nw /etc/hosts
[1]+ Stopped sudo emacs -nw /etc/hosts
$ fg
I was actually surpised by the original post, since I've never
seen that behavior before...
Paul, if you re-read the original post:
http://mail.gnhlug.org/mailman/private/gnhlug-discuss/2007-January/017578.html
...you'll see that you're not talking about the same behavior
described by
On 1/7/07, Michael ODonnell [EMAIL PROTECTED] wrote:
Despite the Subject: line the OP's examples
never illustrated any inability to foreground his Emacs process.
Hmmm, but he did imply that he was unable to foreground it. You
suppose it was just a brain fart, and the OP never actually tried
I've finished sorting through the box o' misfit toys that I picked
up from Brian Karas. There are a few extra things he threw in which
I don't have a reason to keep. If anyone wants any of this, mail me
off-list to arrange pick-up.
In decreasing order of approximate expected value:
