From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: update-subdirs and lisp/term
Date: Sun, 27 Sep 2009 12:35:32 +0200 [thread overview]
Message-ID: <83bpkwsmiz.fsf@gnu.org> (raw)
In-Reply-To: <m28wg03kjj.fsf@whitebox.home>
> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Sun, 27 Sep 2009 09:37:36 +0200
> Cc: emacs-devel@gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> >>
> >> >> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> >> >>
> >> >> >> >> >> > A remnant from past, perhaps, when lisp/term held only
> >> >> >> >> >> > terminal-specific files?
> >> >> >> >> >>
> >> >> >> >> >> Doesn't it still do?
> >> >> >> >> >
> >> >> >> >> > No.
> >> >> >> >>
> >> >> >> >> In which way?
> >> >> >> >
> >> >> >> > All of them.
> >> >> >>
> >> >> >> Please expand. In which way is term/vt100.el not terminal-specific?
> >> >> >
> >> >> > I didn't mean vt100.el (or its ilk).
> >> >>
> >> >> ??? But it is one of them.
> >> >
> >> > Yes, but not the only one.
> >>
> >> But you said "all of them", which includes vt100.el.
> >
> > "All of them" was a response to the question "in which way". IOW,
> > "in all of the ways", not "all of the files".
>
> But they are all terminal-specific in some way.
No, only some of them. Others are non-specific in all ways.
next prev parent reply other threads:[~2009-09-27 10:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 9:48 update-subdirs and lisp/term Eli Zaretskii
2009-09-26 10:44 ` Andreas Schwab
2009-09-26 11:16 ` Eli Zaretskii
2009-09-26 13:24 ` Andreas Schwab
2009-09-26 16:13 ` Eli Zaretskii
2009-09-26 17:55 ` Andreas Schwab
2009-09-26 18:41 ` Eli Zaretskii
2009-09-26 18:46 ` Andreas Schwab
2009-09-26 20:14 ` Eli Zaretskii
2009-09-26 20:59 ` Andreas Schwab
2009-09-26 21:06 ` Eli Zaretskii
2009-09-26 21:07 ` Andreas Schwab
2009-09-27 7:29 ` Eli Zaretskii
2009-09-27 7:37 ` Andreas Schwab
2009-09-27 10:35 ` Eli Zaretskii [this message]
2009-09-27 11:13 ` Andreas Schwab
2009-09-27 12:39 ` Richard Stallman
2009-09-26 21:04 ` Stefan Monnier
2009-09-27 7:28 ` Eli Zaretskii
2009-09-27 18:12 ` Stefan Monnier
2009-09-27 19:09 ` Eli Zaretskii
2009-09-27 22:55 ` Stefan Monnier
2009-09-26 14:07 ` Stefan Monnier
2009-09-26 16:19 ` Eli Zaretskii
2009-09-26 16:45 ` Dan Nicolaescu
2009-09-26 16:53 ` Chong Yidong
2009-09-26 21:03 ` Stefan Monnier
2009-09-29 9:19 ` Carsten Dominik
2009-09-26 21:01 ` Stefan Monnier
2009-09-28 3:43 ` Richard Stallman
2009-09-28 6:36 ` Eli Zaretskii
2009-09-28 21:58 ` Richard Stallman
2009-09-28 22:10 ` joakim
2009-09-28 22:15 ` Chong Yidong
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=83bpkwsmiz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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).