all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: tramp-compat-funcall -> compat-funcall?
Date: Thu, 22 Sep 2016 14:23:45 -0400	[thread overview]
Message-ID: <jwv7fa3sslx.fsf-monnier+Inbox@gnu.org> (raw)
In-Reply-To: <874m57lt1b.fsf@gmx.de> (Michael Albinus's message of "Thu, 22 Sep 2016 19:54:08 +0200")

>>>> IOW, if there's a kind of situation that recurs often enough to warrant
>>>> something like (tramp-)compat-funcall you should report this as a bug.
>>> `tramp-compat-funcall' is almost used for backward compatibility.
>>> Who shall be the target of a bug report then?
>> M-x report-emacs-bug.
> Package: Emacs
> Version: 23.1

If you want the warning to be fixed in Emacs-23.1 then indeed I won't
help you (I think it's a waste of time).

But if you want to eliminate the warning (about code that should work in
Emacs-23) in Emacs-25/26 then `M-x report-emacs-bug` is a good way to
ask for that.


        Stefan



  reply	other threads:[~2016-09-22 18:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 11:04 tramp-compat-funcall -> compat-funcall? Ted Zlatanov
2016-09-22 12:31 ` Stefan Monnier
2016-09-22 13:22   ` Michael Albinus
2016-09-22 17:46     ` Stefan Monnier
2016-09-22 17:54       ` Michael Albinus
2016-09-22 18:23         ` Stefan Monnier [this message]
2016-09-22 20:18   ` Ted Zlatanov
2016-09-23 15:49     ` Stefan Monnier
2016-09-24  6:54       ` Michael Albinus
2016-09-24 13:57         ` Stefan Monnier
2016-09-24 15:39           ` Michael Albinus
2016-09-24 18:40             ` Stefan Monnier
2016-09-25 11:44               ` Michael Albinus
2016-09-25 14:00                 ` Stefan Monnier
2016-09-25 17:23                   ` Ted Zlatanov
2016-09-24 22:42           ` Ted Zlatanov
2016-09-25 14:17             ` Stefan Monnier

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=jwv7fa3sslx.fsf-monnier+Inbox@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.