unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: luangruo@yahoo.com, rrandresf@gmail.com, jnorden@tntech.edu,
	emacs-devel@gnu.org
Subject: Re: longtime user of emacs
Date: Wed, 15 Jul 2020 17:23:11 +0300	[thread overview]
Message-ID: <83wo34luwg.fsf@gnu.org> (raw)
In-Reply-To: <87tuy9l0d1.fsf@localhost> (message from Ihor Radchenko on Wed, 15 Jul 2020 15:10:34 +0800)

> From: Ihor Radchenko <yantar92@gmail.com>
> Date: Wed, 15 Jul 2020 15:10:34 +0800
> Cc: "andres.ramirez" <rrandresf@gmail.com>, Jeff Norden <jnorden@tntech.edu>,
>  emacs-devel@gnu.org
> 
> Some thoughts:
> 1. The link to the tour in the welcome page is not easy to spot for a
> new user. There is too much information. I might be better to show it by
> default on first startup after installation.
> 2. Currently, the tour is one long web-page, which is not very easy to
> read. I imagine that a presentation-like style (with prev/next buttons
> on each page) showing one concept at a time would be easier to read.
> 3. The tour may as well include interactive customisation. For example,
> 'Migrating to Emacs' part of the tour may as well contain a clickable
> element to turn on CUA mode by default.
> 4. The tour might ask user questions if the user is going to work with
> source code, email, web-browsing, shell, etc. If the user is not
> planning to work with certain things, they may as well be hidden from
> menu and customisation pages. By hidden I don't mean completely hidden,
> but rather "folded" - the user should be able to show them back.
> For a newcomer, Emacs offers very too many different options. I believe
> that it makes more sense to restrict the customisation and menus to what
> user explicitly plans to do. It should be already more than enough to
> start learning.
> 5. Similar guided tours may be created for most popular Emacs features:
>    - working with source code
>    - org-mode
>    - version-control and collaboration
>    - remote file access
>    - mail
>    Those tours might also offer some initial customisation, so that the
>    user may disable/enable some features which are not relevant to
>    his/her workflow.
>    The guides should be easily accessible from menu.
> 6. Some new users might be confused by default file open dialogie
> involving mode-line. I believe that similarly to CUA-mode, Emacs can
> emulate more standard approach by offering dired as a way to open files
> (not enabled by default, but offered as a customisation together with
> CUA-mode).

Thank you for writing this.  I would encourage interested people to
work on some of these ideas.



  reply	other threads:[~2020-07-15 14:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 17:09 "Why is emacs so square?" Jeff Norden
2020-05-26 23:17 ` Dmitry Gutov
2020-05-29 14:27 ` Arthur Miller
2020-07-13 22:36 ` Jeff Norden
2020-07-13 23:37   ` Jeff Norden
2020-07-14  0:12     ` longtime user of emacs (was: "Why is emacs so square?") andres.ramirez
2020-07-14  0:39       ` longtime user of emacs Po Lu
2020-07-14  3:58       ` longtime user of emacs (was: "Why is emacs so square?") Jeff Norden
2020-07-14  5:14         ` Ihor Radchenko
2020-07-15  5:44           ` longtime user of emacs Po Lu
2020-07-15  7:10             ` Ihor Radchenko
2020-07-15 14:23               ` Eli Zaretskii [this message]
2020-07-14 21:21         ` longtime user of emacs (was: "Why is emacs so square?") andrés ramírez

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=83wo34luwg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jnorden@tntech.edu \
    --cc=luangruo@yahoo.com \
    --cc=rrandresf@gmail.com \
    --cc=yantar92@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).