From: michael-franzese@gmx.com
To: michael-franzese@gmx.com
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>, Jean Louis <bugs@gnu.support>
Subject: Re: Changing outline-minor-mode keybindings for texinfo files
Date: Fri, 14 May 2021 14:24:00 +0200 [thread overview]
Message-ID: <trinity-d8c78002-4c3c-40b9-b7f8-30d4fb5ffa6c-1620995040037@3c-app-mailcom-bs04> (raw)
In-Reply-To: <trinity-a2fc17d0-a923-4cd4-b5d4-920de7796ced-1620986667580@3c-app-mailcom-bs04>
> Sent: Friday, May 14, 2021 at 10:04 PM
> From: michael-franzese@gmx.com
> To: "Jean Louis" <bugs@gnu.support>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Changing outline-minor-mode keybindings for texinfo files
>
> > Sent: Friday, May 14, 2021 at 9:51 PM
> > From: "Jean Louis" <bugs@gnu.support>
> > To: michael-franzese@gmx.com
> > Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> > Subject: Re: Changing outline-minor-mode keybindings for texinfo files
> >
> > * michael-franzese@gmx.com <michael-franzese@gmx.com> [2021-05-14 10:29]:
> > > Have coded things this way. Then I load a texi file and press "H-q",
> > > but I get "H-q is undefined".
> > >
> > > (defun vmove-keytrigger ()
> > > "Visualises outline and moves texinfo code."
> > >
> > > (let ( (map texinfo-mode-map) )
> > > (define-key map (kbd "H-q") #'outline-hide-sublevels)
> > > (define-key map (kbd "H-b") #'outline-hide-body)
> > > (define-key map (kbd "H-<up>") #'outline-move-subtree-up)
> > > (define-key map (kbd "H-<down>") #'outline-move-subtree-down)
> > > ))
> >
> > You define function but I without giving result out. You copy
> > texinfo-mode-map to map, and change the map, but after that all
> > changes are lost in such function that yields with nothing.
>
> Would I need add-hook of some kind?
How does one go about this thing of using different keybindings rather than
the long version "C-c @ ..."?
> > --
> > Jean
> >
> > Take action in Free Software Foundation campaigns:
> > https://www.fsf.org/campaigns
> >
> > Sign an open letter in support of Richard M. Stallman
> > https://stallmansupport.org/
> > https://rms-support-letter.github.io/
> >
> >
>
>
next prev parent reply other threads:[~2021-05-14 12:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 5:47 Changing outline-minor-mode keybindings for texinfo files michael-franzese
2021-05-14 7:28 ` michael-franzese
2021-05-14 9:51 ` Jean Louis
2021-05-14 10:04 ` michael-franzese
2021-05-14 12:24 ` michael-franzese [this message]
2021-05-14 13:31 ` michael-franzese
2021-05-14 14:03 ` Jean Louis
2021-05-14 16:00 ` Yuri Khan
2021-05-14 16:19 ` michael-franzese
2021-05-14 18:49 ` Jean Louis
2021-05-15 21:10 ` tomas
2021-05-14 16:20 ` Yuri Khan
2021-05-14 16:36 ` michael-franzese
2021-05-14 20:10 ` Yuri Khan
2021-05-15 5:25 ` michael-franzese
2021-05-15 5:58 ` Yuri Khan
2021-05-15 6:07 ` michael-franzese
2021-05-15 6:35 ` Yuri Khan
2021-05-15 5:59 ` michael-franzese
2021-05-15 6:02 ` Yuri Khan
2021-05-15 6:21 ` michael-franzese
2021-05-15 6:36 ` Yuri Khan
2021-05-15 8:40 ` michael-franzese
2021-05-15 9:00 ` Yuri Khan
2021-05-15 10:48 ` michael-franzese
2021-05-14 18:13 ` michael-franzese
2021-05-14 13:55 ` Jean Louis
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-d8c78002-4c3c-40b9-b7f8-30d4fb5ffa6c-1620995040037@3c-app-mailcom-bs04 \
--to=michael-franzese@gmx.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@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.
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).