From: d@teklibre.org (Dave Täht)
To: tycho garen <garen@tychoish.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Emacs 21.4.1 support
Date: Mon, 14 Sep 2009 19:10:24 -0600 [thread overview]
Message-ID: <878wghf1xb.fsf@mahal.sjds.teklibre.org> (raw)
In-Reply-To: <20090914201516.GQ9795@newton.linlan> (tycho garen's message of "Mon, 14 Sep 2009 16:15:16 -0400")
tycho garen <garen@tychoish.com> writes:
> On Mon, Sep 14, 2009 at 12:59:53PM -0600, Dave Täht wrote:
>> "Jing Su @ Gmail" <Jing.Su.66@gmail.com> writes:
>> >
>> > I fully understand that Emacs 21 is way out of date. However, since
>> > RHEL is one of the mainstream commercial distros, and is common on
>> > servers, it would be great if org-mode can be consistent with such
>> > industrial standard'' (which is always way out of date :S ). System
>> > administrators will take risk to install unofficial org-mode, but most
>> > of them won't risk the whole server, i.e., risk their necks, for a
>> > newer but unofficial (according to RH) Emacs version.
>> >
>>
>> No, to heck with that. Most serious users of emacs end up compiling
>> their own release, at least until recently, because the official
>> releases were so out of date. I would suggest pulling current rpms from
>> fedora (maybe they have the equivalent of emacs-snapshot?) And tying
>> those on rhel.
>
> A couple of things. Most significantly, I think it's important to
> avoid being so blase about supporting this subset of users,
> particularly when the answers--with a little bit of digging--are
> pretty simple. Having said that, there's a bunch of stuff that
> probably won't work, I would offer a number of other possible
> solution.
You are right, but I have found the default install of emacs to be so
lame on so many distros for so long that I can understand why people
have flocked to other editors.
Take, for example, the fact that no distro that I know of installs an
emacs compatible ansi-term entry in terminfo by default. (Couple that
with the fact that no terminal emulator I have found in emacs works as
good as the equivalent in xterm, gnome-terminal, etc. It's really
bugging me at the moment, actually, I'd really like to use ansi-term but
every time I try it ends up spewing data all on the same line after a
while. I swear I had it working well for a few days with 23.1 but then I
went back to emacs-snapshot because I didn't want to build everything
Emacs-snapshot did for me)
Multiply by the huge number of packages required to make emacs
competitive with eclipse, like semantic. Stir in missing-by-default
emacs modes like Python mode.
Compare with the bundled supported moduls of vim for system
administration and basic programming tasks. Simmer,
then run away.
Org is the first truly compelling application that emacs has had in years.
>
> First, I'd look at EPEL, rather than Fedora as a source for RHEL
> packages of more recent emacsen to use. If you can get a version of
> emacs 22.(something) there's a version of org-mode included with that
> version. So a little hop should be enough to get you basic
> functionality.
>
Cool, I wasn't aware of that.
> If you're running on servers, as it sounds like you are, getting
> graphical support for all the new things that have happened in the
> last two version of emacs, might be easier. So that while a lot of
> things have changed in emacs in the last four years, the subset of
> things in emacs that have changed in the terminal mode, might be
> somewhat smaller. And really since org-mode is mostly compatible with
> emacs22 still (right?), the barrier might be even lower than many
> people think, particularly if you're not going for *full
> functionality*.
That was the point I tried to make earlier, but wasn't clear. I rarely run
emacs on the server at all, preferring to use tramp to access files
elsewhere. (And things like pdsh, but I digress)
>
> Having said that, how much emacs hacekry do people do on servers. Even
> though I have emacs23-nox installed on my server, I must say that most
> of my text-file-editing on the server happens in Zile, which is
> just emacs-like enough for me to avoid pulling my hair out, but very
> small/lightweight. So I guess after all of that I'm not sure that I
> see the use-case you propose.
>
> As an aside, I think OS X ships with emacs21, so it's not just RHEL,
I've seen that version on a mac. It's sadly deficient.
Every serious emacs user on a mac I know immediately installed aquamacs or a
more modern gnu emacs.
The unserious users just went away.
> but I think that more people are willing to tinker with OS X than they
> are willing to tinker with RHEL. But, if someone is willing to package
Heh. RHEL is there to be an OS you don't worry about, ever, but don't
use for anything new and interesting. It has a valid role in life but is
currently awfully long in the tooth.
> (or use the OpenSuSE build process) to make org-mode/emacs23 packages
> for RHEL I think sysadmins might be more willing to give it a try,
> given the wonders of (quasi)modern package management.
>
> Cheers,
> tycho
--
Dave Taht
http://the-edge.blogspot.com
next prev parent reply other threads:[~2009-09-15 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 17:45 Emacs 21.4.1 support Jing Su @ Gmail
2009-09-14 18:59 ` Dave Täht
2009-09-14 20:15 ` tycho garen
2009-09-15 1:10 ` Dave Täht [this message]
2009-09-15 1:21 ` Eric Schulte
2009-09-14 19:13 ` Tassilo Horn
2009-09-14 20:03 ` Andrew Stribblehill
2009-09-14 22:35 ` Leo
2009-09-14 23:08 ` Carsten Dominik
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=878wghf1xb.fsf@mahal.sjds.teklibre.org \
--to=d@teklibre.org \
--cc=emacs-orgmode@gnu.org \
--cc=garen@tychoish.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).