From: Gregor Zattler <grfz@gmx.de>
To: 49605@debbugs.gnu.org
Subject: bug#49605: 28.0.50; *Shortdoc buffer*: 'n', 'p' not working as expected
Date: Sat, 17 Jul 2021 14:51:20 +0200 [thread overview]
Message-ID: <87tuktyugn.fsf@no.workgroup> (raw)
Dear emacs developers, I recently learned about shordoc.el
When testing it I realized that keys 'n', 'p', bound to
shortdoc-next and shortdoc-previous respectively do not move
point to the next or previous example in the buffer, but to
BoB and EoB respectively.
Thanks for your attention, Gregor
In GNU Emacs 28.0.50 (build 4, x86_64-pc-linux-gnu, X toolkit, cairo version 1.16.0)
of 2021-07-17 built on no
Repository revision: 109c27341e35fae778b95e0eb5d4d72927bf4ea8
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12004000
System Description: Debian GNU/Linux 10 (buster)
Configured using:
'configure -C --prefix=/usr/local/stow/emacs-snapshot
--prefix=/usr/local/stow/emacs-snapshot
--enable-locallisppath=/etc/emacs:/usr/local/share/emacs/28.0/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/28.0/site-lisp:/usr/share/emacs/site-lisp
--with-sound=yes --without-gconf --with-mailutils --build
x86_64-linux-gnu
--infodir=/usr/local/share/info:/usr/share/info
--with-pop=yes --with-cairo --with-x=yes
--with-x-toolkit=lucid --without-toolkit-scroll-bars
--enable-checking=yes --enable-check-lisp-object-type=yes
--with-native-compilation'
Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS
HARFBUZZ JPEG JSON LCMS2 LIBOTF LIBSELINUX LIBSYSTEMD
LIBXML2 M17N_FLT MODULES NATIVE_COMP NOTIFY INOTIFY PDUMPER
PNG RSVG SECCOMP SOUND THREADS TIFF X11 XAW3D XDBE XIM XPM
LUCID ZLIB
next reply other threads:[~2021-07-17 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 12:51 Gregor Zattler [this message]
2021-07-17 13:42 ` bug#49605: 28.0.50; *Shortdoc buffer*: 'n', 'p' not working as expected Lars Ingebrigtsen
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=87tuktyugn.fsf@no.workgroup \
--to=grfz@gmx.de \
--cc=49605@debbugs.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.
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.