From: Dan Nicolaescu <dann@ics.uci.edu>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: what is TERM?
Date: Sun, 13 Jul 2008 08:37:35 -0700 [thread overview]
Message-ID: <200807131537.m6DFbZpR024814@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <857ibplt6l.fsf@lola.goethe.zz> (David Kastrup's message of "Sun, 13 Jul 2008 17:06:42 +0200")
David Kastrup <dak@gnu.org> writes:
> Dan Nicolaescu <dann@ics.uci.edu> writes:
>
> > Does anyone know what the #ifdef TERM code in src/s/gnu-linux.h is
> > supposed to do?
> >
> > process.c has this:
> > /* TERM is a poor-man's SLIP, used on GNU/Linux. */
> > #ifdef TERM
> > #include <client.h>
> > #endif
> >
> > Nothing defines TERM, so can all the code that depends on it go?
>
> You can compile with -DTERM, I suppose. term is a serial line
> communications program not requiring administrator priviledges used for
> tunneling TCP ports to a normal dialup modem login. Since no admin
> rights are required for tunneling, the local programs need to be
> recompiled with a special library so that they try looking up the ports
> on the other side first.
>
> In that manner, one can, for example, use Emacs on the local machine for
> reading Usenet and sending Mail to the remote machine where one just has
> a normal terminal account.
>
> It is probably not used all too much anymore: pure terminal dialups have
> become rather rare. One reference I found on the web is
> <URL:http://www.cit.gu.edu.au/~anthony/info/usage/term_howto.html>.
Thanks for the detailed explanation!
So is it worth keeping this code?
To use this code one would have to hack the build system to use an
undocumented flag (-DTERM), and to want to use network connections in
emacs in a not very common setup.
next prev parent reply other threads:[~2008-07-13 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 14:32 what is TERM? Dan Nicolaescu
2008-07-13 15:06 ` David Kastrup
2008-07-13 15:37 ` Dan Nicolaescu [this message]
2008-07-13 16:00 ` David Kastrup
2008-08-30 2:16 ` Daniel Colascione
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=200807131537.m6DFbZpR024814@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=dak@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).