From: Jean Louis <bugs@gnu.support>
To: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
Cc: emacs-tangents@gnu.org
Subject: Re: 2021-05-03 Emacs news
Date: Thu, 6 May 2021 08:54:02 +0300 [thread overview]
Message-ID: <YJOEekL36UF8Zns1@protected.localdomain> (raw)
In-Reply-To: <TY2PR0101MB36930814427C5375824676D0DA5A9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com>
* Ramesh Nedunchezian <rameshnedunchezian@outlook.com> [2021-05-04 10:02]:
>
> Summary: Helm now has "official" info and html documents.
>
> Now the Helm documents are available in info format. The texi2html
> pages are available on Helm's official website.
>
> https://emacs-helm.github.io/helm/doc/index.html
>
> The documentation is in Org format and TexInfo manuals are created
> using ox-texinfo.el, so learning texinfo shouldn't be a barrier to
> improving the current documentation.
I like Helm and used it much. But then I realized I don't want
programs be locked to Helm, so I have liberated them so that any kind
of completion may be used.
Documentation on that website starts with technical things, not
so practical, that practical part is there but rather hidden, harder
to find. Helm should start with simplest explanation including with
the animation showing how it works.
The actual start of programming with Helm is so much simpler than what
is facing me as reader on that page.
If any package is visual, that is Helm. It should speak visually to
reader, instead of expectation that reader already knows everything
about it.
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/
prev parent reply other threads:[~2021-05-06 5:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 4:49 2021-05-03 Emacs news Sacha Chua
2021-05-04 5:46 ` Ramesh Nedunchezian
2021-05-06 5:54 ` Jean Louis [this message]
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=YJOEekL36UF8Zns1@protected.localdomain \
--to=bugs@gnu.support \
--cc=emacs-tangents@gnu.org \
--cc=rameshnedunchezian@outlook.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).