From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: How to IRC?
Date: Thu, 17 Dec 2015 02:04:29 +0100 [thread overview]
Message-ID: <87bn9p51ia.fsf@debian.uxu> (raw)
In-Reply-To: 87k2oe5rwr.fsf@ulb.ac.be
Nicolas Richard <nrichard@ulb.ac.be> writes:
> An IRC client can have bugs
No :)
> That being said, I never noticed any such
> disconnection problem with rcirc, which I use.
> Some people on #emacs use ERC with a very impressive
> uptime too, so I doubt rcirc or ERC have this sort
> of bugs.
I doubt that as well. Anyway, look (!) - uptime again!
It is such a useful thing :)
> OTOH, since emacs has only one lisp thread, when
> emacs is doing something, it will most likely stop
> responding to ping requests and, if it emacs is busy
> long enough, this can lead to disconnection.
> A common suggestion (even though I don't follow it)
> is to use a separate emacs session only for IRC.
That might be a good solution with respect to uptime
but not with respect to using Emacs and ERC/IRC to do
useful things. Say that you work on some source and
you want to yank it into the ERC buffer. Or the other
way around.
I'd say in general it is preferrable to do it the
other way around - keep everything including ERC/IRC
in the regular Emacs session, and then, for the rare
occasions when you use Emacs for batch/DP stuff that
might block IRC, put *that* in its own session.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-12-17 1:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1218.1449153433.31583.help-gnu-emacs@gnu.org>
2015-12-03 15:59 ` How to IRC? Pascal J. Bourguignon
2015-12-04 0:55 ` Emanuel Berg
2015-12-04 22:03 ` B. T. Raven
2015-12-05 1:57 ` Emanuel Berg
2015-12-16 15:34 ` Nicolas Richard
2015-12-17 1:04 ` Emanuel Berg [this message]
[not found] ` <mailman.17.1450280146.843.help-gnu-emacs@gnu.org>
2015-12-17 2:20 ` B. T. Raven
2015-12-17 2:57 ` Emanuel Berg
2015-12-03 14:36 Marcin Borkowski
2015-12-03 15:58 ` Aurélien Aptel
2015-12-03 16:18 ` Teemu Likonen
2015-12-03 18:13 ` Marcin Borkowski
2015-12-03 18:22 ` Teemu Likonen
2015-12-03 20:15 ` Marcin Borkowski
2015-12-03 22:05 ` Teemu Likonen
2015-12-04 11:46 ` Jude DaShiell
2015-12-04 0:50 ` Emanuel Berg
2015-12-04 0:45 ` Emanuel Berg
2015-12-10 4:23 ` Shakthi Kannan
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bn9p51ia.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).