From: Peter Vasil <mailing_lists@petervasil.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 14860@debbugs.gnu.org
Subject: bug#14860: [Peter Vasil] emacs 24.3.50.1: Byte compile warning Warning: function used to take 0+ arguments, now takes 0
Date: Sun, 14 Jul 2013 20:28:05 +0200 [thread overview]
Message-ID: <CAJe0aUQQyL4Vu4TOtLv+vWsPmx9wKXPVv6bUbXKCQpErPBf29Q@mail.gmail.com> (raw)
In-Reply-To: <jwvzjtpdoqh.fsf-monnier+emacs@gnu.org>
I had the advice only because I adviced the regular goto-line to call
hs-show-block and when I added the got-line-with-feedback I just
copied the first advice and did not realize that it makes no sense. I
have removed the advice now and I've put the hs-show-block into
got-line-with-feedback function.
Sorry for the noise.
Peter
On Sun, Jul 14, 2013 at 7:41 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> Indeed, I have an advice on that function
>> (defadvice goto-line-with-feedback
>> (after
>> expand-after-goto-line-with-feedback
>> activate compile)
>> "hideshow-expand affected block when using
>> goto-line-with-feedback in a collapsed buffer"
>> (save-excursion
>> (hs-show-block)))
>
> Than it's a known issue. I do wonder, tho: why on earth do you have an
> advice on your hand-written function?
>
>
> Stefan
next prev parent reply other threads:[~2013-07-14 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJe0aUTtUyT8fhnJyg=kWLcD1VaCAS95pHTLxXwhE1J+wZBtzw@mail.gmail.com>
2013-07-14 17:41 ` bug#14860: [Peter Vasil] emacs 24.3.50.1: Byte compile warning Warning: function used to take 0+ arguments, now takes 0 Stefan Monnier
2013-07-14 18:28 ` Peter Vasil [this message]
2013-07-13 23:35 Stefan Monnier
2013-07-14 0:02 ` Stefan Monnier
2013-07-14 1:03 ` Michael Heerdegen
2013-07-14 6:34 ` Stefan Monnier
2013-07-14 9:09 ` Peter Vasil
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=CAJe0aUQQyL4Vu4TOtLv+vWsPmx9wKXPVv6bUbXKCQpErPBf29Q@mail.gmail.com \
--to=mailing_lists@petervasil.net \
--cc=14860@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.