unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: michael-franzese@gmx.com
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Changing outline-minor-mode keybindings for texinfo files
Date: Fri, 14 May 2021 18:19:04 +0200	[thread overview]
Message-ID: <trinity-8ddca68e-b73d-4f5f-be9f-906b7d42656b-1621009144726@3c-app-mailcom-bs04> (raw)
In-Reply-To: <CAP_d_8WknCuCfp2JEYVf=ARYzG5jYgk0ga_HHRQVmsjxRVsY0A@mail.gmail.com>



> Sent: Saturday, May 15, 2021 at 4:00 AM
> From: "Yuri Khan" <yuri.v.khan@gmail.com>
> To: michael-franzese@gmx.com, "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Changing outline-minor-mode keybindings for texinfo files
>
> On Fri, 14 May 2021 at 21:06, Jean Louis <bugs@gnu.support> wrote:
> 
> > > (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) ))
> > >
> > > (add-hook 'texinfo-mode-hook 'vmove-keytrigger)
> >
> > In my opinion that hook, when it runs, internally get that all
> > defined, but once function finishes, nothing yields out of it, because
> > it is within `let' enclosure and because you are working on a
> > temporary variable `map'.
> 
> No, because ‘map’ is a reference to the same object that
> ‘texinfo-mode-map’ refers to. Within the functions, they are two names
> of the same data structure. Changes made through one name within the
> function are then visible through the other name after the function
> returns.

So it is good?



  reply	other threads:[~2021-05-14 16:19 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
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 [this message]
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-8ddca68e-b73d-4f5f-be9f-906b7d42656b-1621009144726@3c-app-mailcom-bs04 \
    --to=michael-franzese@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=yuri.v.khan@gmail.com \
    /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).