From: Christopher Dimech <dimech@gmx.com>
To: Jean Louis <bugs@gnu.support>, George Mauer <gmauer@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: A dream?
Date: Sat, 15 Apr 2023 21:36:27 +0200 [thread overview]
Message-ID: <trinity-508b1688-dc2e-440b-8f28-3c2ee27c9a36-1681587387229@3c-app-mailcom-bs12> (raw)
In-Reply-To: <ZDoI84l65XvsX75G@protected.localdomain>
> Sent: Saturday, April 15, 2023 at 2:16 PM
> From: "Jean Louis" <bugs@gnu.support>
> To: "George Mauer" <gmauer@gmail.com>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: A dream?
>
> * George Mauer <gmauer@gmail.com> [2023-04-03 18:17]:
> > Emacs is a complex tool that itself can take a semester or more to get
> > productive in. I know I myself tried for years to move to it and was only
> > able to after learning vim bindings pretty well, and starting to use
> > Spacemacs. Forcing students to use emacs, much less org - especially in
> > this day and age where students *will* ask online, and *will* get a
> > response of "no one actually uses that" - will probably meet with a ton of
> > resistance.
We ran it on the International Space Station. If that is the response of students,
then they are lame bro,
> We have got no problem to let staff members use Emacs in East
> Africa. I have not get any protest yet, people are interested.
>
> I have seen American surgeon and his brother from university totally
> delighted with the usage of Emacs and "how everything works in one
> program". They kept asking what is it.
>
> Here is how to verify usability of Emacs, once you verify it, let us
> know:
>
> Usability 101: Introduction to Usability:
> https://www.nngroup.com/articles/usability-101-introduction-to-usability/
>
> How Many Test Users in a Usability Study?:
> https://www.nngroup.com/articles/how-many-test-users/
>
> Usability Testing 101:
> https://www.nngroup.com/articles/usability-testing-101/
>
> --
> Jean
>
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
>
> In support of Richard M. Stallman
> https://stallmansupport.org/
>
>
next prev parent reply other threads:[~2023-04-15 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 13:52 A dream? Marko Schuetz-Schmuck
2023-04-03 14:27 ` Rob Sargent
2023-04-03 15:11 ` indieterminacy
2023-04-03 15:16 ` George Mauer
2023-04-15 2:16 ` Jean Louis
2023-04-15 19:36 ` Christopher Dimech [this message]
2023-04-15 22:33 ` Dr. Arne Babenhauserheide
2023-04-15 23:10 ` Christopher Dimech
2023-04-17 6:26 ` Jean Louis
2023-04-15 22:43 ` Eduardo Ochs
2023-04-17 6:30 ` Jean Louis
2023-04-03 15:22 ` Martin Steffen
-- strict thread matches above, loose matches on Subject: below --
2023-04-04 10:12 Pedro Andres Aranda Gutierrez
2023-04-18 5:35 Pedro Andres Aranda Gutierrez
2023-04-18 12:40 ` Adolfo De Unanue
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-508b1688-dc2e-440b-8f28-3c2ee27c9a36-1681587387229@3c-app-mailcom-bs12 \
--to=dimech@gmx.com \
--cc=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=gmauer@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/org-mode.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).