all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
Cc: 38730@debbugs.gnu.org
Subject: bug#38730: 27.0.50; tutorial start does not take into account the  customization notice
Date: Tue, 24 Dec 2019 17:41:40 +0200	[thread overview]
Message-ID: <83blrxwx1n.fsf@gnu.org> (raw)
In-Reply-To: <441821C4-EE9B-40E8-970A-13B3C720C07D@traduction-libre.org> (message from Jean-Christophe Helary on Tue, 24 Dec 2019 18:37:57 +0900)

> From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
> Date: Tue, 24 Dec 2019 18:37:57 +0900
> 
> When starting the Tutorial in an emacs session that has modified
> keybindings, an information notice is displayed in red/bold characters at the top of the screen.
> 
> That notice pushes the first step of the tutorial to below the visible space of the frame. The user thus cannot see the first step and has to manually scroll down to see it, which defeats the purpose of that first step where the user learns to use C-v to move one screenful down...

I'm not sure what use case is described here.  If keybindings have
been modified, we probably aren't talking about a complete newcomer to
Emacs, so at least simple cursor motion should already be a skill
he/she already acquired, right?  He/she might already know to scroll
with PgDn or the mouse wheel, right?

OTOH, in a customized session, we can reasonably expect to see a
window that is larger than the default shown by "emacs -Q", and maybe
then the beginning of the tutorial will still be visible?

And if none of the above helps, then what kind of solution would you
propose for such a situation?





  reply	other threads:[~2019-12-24 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24  9:37 bug#38730: 27.0.50; tutorial start does not take into account the customization notice Jean-Christophe Helary
2019-12-24 15:41 ` Eli Zaretskii [this message]
2020-08-25 22:57   ` Stefan Kangas

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=83blrxwx1n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=38730@debbugs.gnu.org \
    --cc=jean.christophe.helary@traduction-libre.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.