emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [DEV] Bump Emacs requirement to 24.4?
Date: Sat, 15 Aug 2015 10:45:54 +0200	[thread overview]
Message-ID: <87oai9c531.fsf@Rainer.invalid> (raw)
In-Reply-To: 87io8tfrtk.fsf@nicolasgoaziou.fr

Nicolas Goaziou writes:
> Just to be sure, can we require Emacs 24.4 for development version
> (a.k.a. Org 8.4)? As a data point, Debian stable provides it.

Debian Squeeze LTS or whatever they call it doesn't w/o backports.
RHEL6 doesn't have it w/o epel (RHEL7 has 24.3 IIRC).
RaspberryPi doesn't have it.

I'm still falling over Emacs 22 in various forms and Emacs 23, where it
is standard is not always at the latest version (23.4).

> Also, what is the status of XEmacs support? AFAIU Org 8.3 doesn't build
> on XEmacs but no one is complaining. We may as well drop it and ignore
> most of "org-compat.el".

I've been doing a lot of this compat stuff, but I gave up since I
couldn't get ERT to work on XEmacs.  Org did build (with lots of errors)
until some point and it was at least superficially usable.  The two
XEmacs users on this list have never responded to any requests for
further testing.  So I guess that XEmacs can be considered
unsupportable.

If you were hoping to get rid of compat, then have a look at the warnings
on Emacs 25.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  parent reply	other threads:[~2015-08-15  8:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 19:39 [DEV] Bump Emacs requirement to 24.4? Nicolas Goaziou
2015-08-05 19:38 ` Kaushal
2015-08-05 21:13 ` Suvayu Ali
2015-08-05 21:51 ` Rasmus
2015-08-06  5:42   ` Robert Klein
2015-08-06  8:03     ` Nicolas Goaziou
2015-08-06  8:23       ` Robert Klein
2015-08-06  8:25       ` Rasmus
2015-08-15  7:21         ` Bastien Guerry
2015-08-15  7:29           ` Nicolas Goaziou
2015-08-15  8:15             ` Bastien Guerry
2015-08-15  8:30               ` Rasmus
2015-08-15  8:37                 ` Bastien Guerry
2015-08-15  9:51                   ` Nicolas Goaziou
2015-08-15 10:02                   ` Rasmus
2015-08-15 12:14                   ` Robert Horn
2015-08-15  9:37               ` Nicolas Goaziou
2015-08-15 14:23                 ` Bastien Guerry
2015-08-15 19:50                   ` Nicolas Goaziou
2015-08-15 23:30                     ` Bastien
2015-08-16  6:08                       ` Achim Gratz
2015-08-16  8:13                         ` Bastien Guerry
2015-08-16 18:03                           ` Achim Gratz
2015-08-18 23:01               ` Bastien
2015-08-19  5:22                 ` David Engster
2015-08-19  9:52                   ` Bastien
2015-08-19  6:04                 ` Suvayu Ali
2015-08-19  9:40                   ` Bastien
2015-08-19 10:31                     ` Suvayu Ali
2015-08-19 16:11                 ` Achim Gratz
2015-08-19 20:07                 ` Rasmus
2015-08-20 23:02                   ` Bastien
2015-09-16  7:58                     ` Rasmus
2015-08-05 22:22 ` Bastien Guerry
2015-08-06  1:07   ` Nicolas Goaziou
2015-08-15  8:45 ` Achim Gratz [this message]
2015-08-15  9:28   ` Nicolas Goaziou

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=87oai9c531.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@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/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).