From: Michael Albinus <michael.albinus@gmx.de>
To: ding@gnus.org
Subject: Re: Emacs version compatibility
Date: Thu, 02 Feb 2012 09:51:59 +0100 [thread overview]
Message-ID: <87vcnpmxcg.fsf@gmx.de> (raw)
In-Reply-To: <87k445ptt5.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 02 Feb 2012 08:40:06 +0100")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Wed, Feb 01 2012, Lars Ingebrigtsen wrote:
>
>> More controversially :-), I think 真 Gnus should also stop defining
>> compatibility functions like `gnus-mark-active-p', and instead just
>> start maintaining a `gnus-compat.el' library that would define functions
>> like `mark-active-p' for Emacsen that don't define them.
>
> Please don't. It violates the Emacs coding guidelines. Packages that
> have gone that road have broken other packages in the past.
> E.g. color-scheme defined `replace-in-string´[1] which broke Gnus and
> emacs-jabber.
1+.
Tramp defines already an own `tramp-compat-delete-directory', in order
to handle the recursive case. It checks for the existence of a proper
`delete-directory' first. I do not want to add another check, whether
the "proper" `delete-directory' comes from gnuis-compat.el (and refuse
to use it then).
> Bye, Reiner.
Best regards, Michael.
next prev parent reply other threads:[~2012-02-02 8:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 13:15 Lars Ingebrigtsen
2012-02-01 13:37 ` Steinar Bang
2012-02-01 18:07 ` Ted Zlatanov
2012-02-01 19:40 ` Lars Ingebrigtsen
2012-02-02 7:40 ` Reiner Steib
2012-02-02 8:51 ` Michael Albinus [this message]
2012-02-02 8:59 ` David Engster
2012-02-02 9:47 ` Lars Ingebrigtsen
2012-02-02 10:43 ` Michael Albinus
2012-02-02 10:51 ` Lars Ingebrigtsen
2012-02-02 12:26 ` Michael Albinus
2012-02-02 12:32 ` Lars Ingebrigtsen
2012-02-02 13:02 ` Michael Albinus
2012-02-02 13:28 ` Lars Ingebrigtsen
2012-02-02 13:39 ` Michael Albinus
2012-02-02 13:03 ` Ted Zlatanov
2012-02-02 13:29 ` Lars Ingebrigtsen
2012-02-02 13:57 ` Ted Zlatanov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vcnpmxcg.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).