From: Jambunathan K <kjambunathan@gmail.com>
To: Nick Dokos <nicholas.dokos@hp.com>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: Emacs 22 compatibility
Date: Sun, 16 Dec 2012 09:57:21 +0530 [thread overview]
Message-ID: <87ehiq62qe.fsf@gmail.com> (raw)
In-Reply-To: <10228.1355612445@alphaville> (Nick Dokos's message of "Sat, 15 Dec 2012 18:00:45 -0500")
Nick Dokos <nicholas.dokos@hp.com> writes:
> Why are they still using emacs-22?
University students and employees.
Sometimes back I was investigating hosting for personal files. The site
runs a version of FreeBSD version and had Emacs 22 on their servers.
When I requested that they upgrade their Emacs to 23 or 24 they refused
citing some reason why they /had/ to downgrade.
It has something to do with their site architecture not supporting
/dev/tty in their ssh environment. Apparently some changes in Emacs 23
- may be Emacs server (or is it the emacsclient?) - that relies on use
of /dev/tty. In short, external constraints.
Also XEmacs seem to be lagging behind severely. See this recent thread:
http://list-archive.xemacs.org/pipermail/xemacs-beta/2012-September/023201.html
I am wondering what makes people continue using their XEmacses.
--
next prev parent reply other threads:[~2012-12-16 4:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 21:25 Emacs 22 compatibility Achim Gratz
2012-12-15 23:00 ` Nick Dokos
2012-12-16 4:27 ` Jambunathan K [this message]
2012-12-16 7:18 ` Achim Gratz
2012-12-18 15:22 ` Bastien
2012-12-18 17:44 ` Achim Gratz
2012-12-18 22:10 ` Yagnesh Raghava Yakkala
2012-12-18 23:29 ` Bastien
2012-12-19 6:46 ` Yagnesh Raghava Yakkala
2012-12-19 9:42 ` Bastien
2012-12-19 9:21 ` Achim Gratz
2012-12-19 9:41 ` Bastien
2012-12-19 10:18 ` Achim Gratz
2012-12-24 12:53 ` Bastien
2012-12-19 18:54 ` Achim Gratz
2012-12-19 19:13 ` Jambunathan K
2012-12-19 19:20 ` Achim Gratz
2012-12-24 12:52 ` Bastien
2012-12-19 19:13 ` Achim Gratz
2012-12-24 13:03 ` Bastien
2012-12-19 19:02 ` Achim Gratz
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ehiq62qe.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/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/org-mode.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).