From: daniela-spit@gmx.it
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org
Subject: Re: Keybinding Cycle for various Capture and Agenda Setups
Date: Mon, 30 Nov 2020 03:57:14 +0100 [thread overview]
Message-ID: <trinity-3810533a-704e-421c-bc89-7e3454b37e33-1606705034170@3c-app-mailcom-bs12> (raw)
In-Reply-To: <87mtyzdcfu.fsf@zoho.eu>
I think I get it now and can make some progress.
> Sent: Sunday, November 29, 2020 at 11:29 PM
> From: "Emanuel Berg via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Keybinding Cycle for various Capture and Agenda Setups
>
> daniela-spit wrote:
>
> >> OK, I have NO IDEA :D what you are doing, but -
> >>
> >>> (defun typh-capture-set-instance (n)
> >>>
> >>> [...]
> >>>
> >>> (defun typh-agenda-set-instance (n)
> >>
> >> but then
> >>
> >>> (typh-capture-set-instance)
> >>>
> >>> [...]
> >>>
> >>> (typh-agenda-set-instance)
> >>
> >> where's the n?
> >
> > Is that the problem?
>
> I don't know if it's _the_ problem or _a_ problem but it is
> a problem alright :)
:)
> Use the byte compiler!
>
> It will tell your that
>
> In typh-cycle-cap-agn:
> ... Warning: typh-capture-set-instance called with 0 arguments, but
> requires 1
> ... Warning: typh-agenda-set-instance called with 0 arguments, but
> requires 1
>
> So step 1, get away with all warnings, and you are one step
> closer to nowhere!
When I worked in France there was a road that took you to the woods,
then stopped.
> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
>
prev parent reply other threads:[~2020-11-30 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 20:13 Keybinding Cycle for various Capture and Agenda Setups daniela-spit
2020-11-29 21:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-29 21:27 ` daniela-spit
2020-11-29 22:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-30 2:57 ` daniela-spit [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-3810533a-704e-421c-bc89-7e3454b37e33-1606705034170@3c-app-mailcom-bs12 \
--to=daniela-spit@gmx.it \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).