unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Johan Myréen" <johan.myreen@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs Survey 2022 - design
Date: Sun, 22 May 2022 11:38:41 +0300	[thread overview]
Message-ID: <CA+TD5hi50gLkVwXBRH7AM0XhCK88ABq0zG_u+n3mkQ0q6tOd1Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

I see there are six editors listed under the question "Which editor did you
use before you started using Emacs?", five of which had an initial release
in this century. Emacs is now 46 years old. Is there a reason for limiting
the choice to these relatively recently created editors?

My answer to the question would have been the "Edit" editor on the TOPS-20
operating system.

Other notable missing choices are the original vi editor and TECO. There
are so many editors in this world that I think a better approach would be
to provide a text area for providing the name of an editor.

Johan Myréen

Ps. Sri Lankan is not the only two word nationality that has been split up,
I spotted Hong and Konger.

[-- Attachment #2: Type: text/html, Size: 874 bytes --]

             reply	other threads:[~2022-05-22  8:38 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22  8:38 Johan Myréen [this message]
2022-05-22 13:03 ` Emacs Survey 2022 - design Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2022-05-17 14:51 Timothy
2022-05-17 15:38 ` Visuwesh
2022-05-19 14:36   ` Timothy
2022-05-17 18:20 ` Stefan Monnier
2022-05-17 19:52   ` Tassilo Horn
2022-05-17 22:21     ` Stefan Monnier
2022-05-18  4:49       ` Tassilo Horn
2022-05-18 12:43         ` Stefan Monnier
2022-05-18 18:47           ` Philip Kaludercic
2022-05-19 14:39   ` Timothy
2022-05-17 18:59 ` Philip Kaludercic
2022-05-19 14:54   ` Timothy
2022-05-19 16:11     ` Philip Kaludercic
2022-05-20  8:11   ` sr
2022-05-20 23:53     ` Philip Kaludercic
2022-05-17 19:43 ` Juri Linkov
2022-05-19 15:13   ` Timothy
2022-05-17 22:16 ` Howard Melman
2022-05-17 22:21 ` Howard Melman
2022-05-17 22:44 ` Will Mengarini
2022-05-17 23:00   ` Stefan Monnier
2022-05-18  0:15     ` Corwin Brust
2022-05-18  7:13       ` Philip Kaludercic
2022-05-19 15:51         ` Timothy
2022-05-19 15:54     ` Timothy
2022-05-19 17:37       ` Stefan Monnier
2022-10-10 17:48         ` Gregor Zattler
2022-05-18  4:39   ` Visuwesh
2022-05-19 15:48     ` Timothy
2022-05-19 15:18   ` Timothy
2022-05-18 11:19 ` Jonas Bernoulli
2022-05-18 18:46   ` Philip Kaludercic
2022-05-19 15:30   ` Timothy
2022-05-18 12:47 ` Jostein Kjønigsen
2022-05-19 15:26   ` Timothy
2022-05-18 22:19 ` Richard Stallman
2022-05-19 15:38   ` Timothy
2022-05-21 22:46     ` Richard Stallman
2022-05-18 22:20 ` Richard Stallman
2022-05-19 15:41   ` Timothy
2022-05-21 22:46     ` Richard Stallman
2022-05-22 11:32       ` Akib Azmain Turja
2022-05-22 12:03         ` Philip Kaludercic
2022-05-19  5:22 ` Mike Kupfer
2022-05-19 15:44   ` Timothy
2022-05-19 16:17     ` Mike Kupfer
2022-05-19 16:01 ` Benjamin Riefenstahl
2022-05-23  8:46 ` Lars Ingebrigtsen
2022-10-02  8:30 ` Timothy
2022-10-02 16:06   ` Philip Kaludercic
2022-10-04  1:00     ` Richard Stallman
2022-10-04  7:00       ` Philip Kaludercic
2022-10-04  7:53         ` Richard Stallman
2022-10-04  8:00   ` Akib Azmain Turja
2022-10-04  8:38     ` Po Lu
2022-10-04  9:37     ` Philip Kaludercic
2022-10-05 16:48   ` Philip Kaludercic

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=CA+TD5hi50gLkVwXBRH7AM0XhCK88ABq0zG_u+n3mkQ0q6tOd1Q@mail.gmail.com \
    --to=johan.myreen@gmail.com \
    --cc=emacs-devel@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 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).