From: Baloff <washdc@wash.edu>
Subject: Re: Gnus threading (was: expand/collapse{} in c++)
Date: 25 Aug 2005 03:36:48 +1000 [thread overview]
Message-ID: <874q9fme33.fsf@wash.edu> (raw)
In-Reply-To: 7quslx0l7ie.fsf@1078-ARIBA-004.central.purdue.lcl
Jason Dufair <jase@dufair.org> writes:
> Baloff <washdc@xxx> writes:
>
> > M-x gnus or even M-x 5 2 gnus, the frame or both frames freeze till it
> > finishes downloading the articles, then I can use emacs, is that the
> > way it is?
>
> I believe this is indeed the way it is. I understand from previous
> newsgroup discussions this is due to the fact that at least some parts
> of Emacs are not multi-threaded and so other internal processes are
> blocking on I/O of some sort.
>
> I have gotten around this process by simply running Gnus in a separate
> Emacs process (and another frame, obviously). Not the most elegant, but
> it does the trick.
> --
> Jason Dufair - jase@dufair.org
how do you start gnus inside an emacs processor right form the shell?
I $emacs& then M-x gnus every time. but even that does now show in
$ps f
PID TTY STAT TIME COMMAND
1066 pts/0 Ss+ 0:00 bash
1574 pts/0 Sl 4:19 \_ /usr/lib/mozilla-firefox/firefox-bin -a firefox
2402 pts/0 S 0:09 \_ emacs
2406 pts/0 S 0:28 \_ emacs
922 tty1 S 0:00 -bash
923 tty1 S+ 0:00 \_ /bin/sh /usr/bin/X11/startx
934 tty1 S+ 0:00 \_ xinit /usr/X11R6/lib/X11/xinit/xinitrc -- /usr/X11R6/lib/X11/xinit/xserverrc
940 tty1 S 0:01 \_ x-session-manager
989 tty1 S 0:00 /usr/bin/gnome-keyring-daemon
986 tty1 S 0:03 /usr/lib/gconf2/gconfd-2 5
> LocalWords: PID
next prev parent reply other threads:[~2005-08-24 17:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 20:00 expand/collapse{} in c++ Baloff
2005-08-23 20:31 ` Gnus threading (was: expand/collapse{} in c++) Jason Dufair
2005-08-24 17:36 ` Baloff [this message]
2005-08-24 19:22 ` Gnus threading Johan Bockgård
2005-08-23 20:47 ` expand/collapse{} in c++ Sébastien Kirche
2005-08-23 21:59 ` Alan Mackenzie
2005-08-26 20:31 ` Baloff
2005-08-26 21:56 ` Peter Lee
2005-08-26 22:00 ` Jason Dufair
2005-08-26 22:39 ` Kevin Rodgers
[not found] ` <mailman.5188.1125098056.20277.help-gnu-emacs@gnu.org>
2005-08-27 8:31 ` Baloff
2005-08-24 3:32 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874q9fme33.fsf@wash.edu \
--to=washdc@wash.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.