Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux > #56901 > unrolled thread

Linux Command-Line Editors Vulnerable to High-Severity Bug

Started by"anonymous" <anonymous@rip.ax.lt>
First post2019-06-16 07:53 -0500
Last post2019-06-25 15:11 +0200
Articles 20 on this page of 244 — 42 participants

Back to article view | Back to alt.os.linux

Contents

  Linux Command-Line Editors Vulnerable to High-Severity Bug "anonymous" <anonymous@rip.ax.lt> - 2019-06-16 07:53 -0500
    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Anonymous" <nobody@mixmin.net> - 2019-06-16 07:56 -0500
    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Fenris <fenris@invalid.invalid> - 2019-06-16 15:53 +0200
      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-06-16 15:35 +0100
        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Roger Blake <rogblake@iname.invalid> - 2019-06-16 15:30 +0000
        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-16 16:53 -0400
      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "School of Agriculture" <ag@hick.edu> - 2019-06-17 14:35 -0500
        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-06-17 20:42 +0100
          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-17 17:31 -0400
        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Roger Blake <rogblake@iname.invalid> - 2019-06-17 20:30 +0000
          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 10:12 +0200
        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug gazelle@shell.xmission.com (Kenny McCormack) - 2019-06-17 20:30 +0000
        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Anonymous" <nobody@mixmin.net> - 2019-06-18 07:04 -0500
          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Fenris <fenris@invalid.invalid> - 2019-06-18 14:18 +0200
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-06-18 14:17 +0100
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug chrisv <chrisv@nospam.invalid> - 2019-06-18 08:52 -0500
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Jasen Betts <jasen@xnet.co.nz> - 2019-06-20 05:57 +0000
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug chrisv <chrisv@nospam.invalid> - 2019-06-20 07:05 -0500
                    Using 'sed' to delete a line from a file (Was: Linux Command-Line Editors Vulnerable to High-Severity Bug) gazelle@shell.xmission.com (Kenny McCormack) - 2019-06-20 12:32 +0000
                      Re: Using 'sed' to delete a line from a file (Was: Linux Command-Line Editors Vulnerable to High-Severity Bug) Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-20 12:17 -0600
                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Anonymous" <anon@anon.com> - 2019-06-20 08:31 -0500
                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Anonymous" <anon@anon.com> - 2019-06-20 08:33 -0500
                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Anonymous" <anon@anon.com> - 2019-06-20 08:42 -0500
    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Sir Gaygory's Owner's Owner 🐶笛 <root@127.0.0.1> - 2019-06-16 11:57 -0500
      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "J.O. Aho" <user@example.net> - 2019-06-16 21:28 +0200
        How come we're not talking about (Was: Linux Command-Line Editors Vulnerable to High-Severity Bug) gazelle@shell.xmission.com (Kenny McCormack) - 2019-06-16 20:12 +0000
          Re: How come we're not talking about (Was: Linux Command-Line Editors Vulnerable to High-Severity Bug) "J.O. Aho" <user@example.net> - 2019-06-17 06:52 +0200
        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Sir Gaygory's Owner's Owner 🐶笛 <root@127.0.0.1> - 2019-06-21 13:24 -0500
    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-16 11:12 -0600
    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Siri Cruise <chine.bleu@yahoo.com> - 2019-06-16 13:26 -0700
      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Snit <usenet@gallopinginsanity.com> - 2019-06-16 13:34 -0700
        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 10:20 +0200
          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-19 10:55 +0200
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 12:37 +0200
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-19 13:13 +0200
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 14:31 +0200
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug ruben safir <ruben@mrbrklyn.com> - 2019-07-20 19:43 -0400
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-19 09:36 -0600
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 14:36 +0200
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug ruben safir <ruben@mrbrklyn.com> - 2019-07-20 19:37 -0400
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2019-06-19 21:32 +0300
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-19 20:47 +0200
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 21:01 +0200
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-06-19 20:23 +0100
                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 22:53 +0200
                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-19 23:09 +0000
                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-20 05:21 +0200
                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-20 04:16 +0000
                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-20 06:21 +0200
                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 14:38 +0200
                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-20 13:30 +0000
                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 19:21 +0200
                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-20 18:39 +0000
                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 22:52 +0200
                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-20 23:48 +0000
                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 13:01 +0200
                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-21 12:30 +0000
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 14:51 +0200
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-21 13:43 +0000
                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E. R." <robin_listas@es.invalid> - 2019-06-23 12:56 +0200
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-21 08:55 -0500
                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 19:01 +0200
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "F. Russell" <frussell@random.info> - 2019-06-21 13:33 +0000
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-21 13:39 +0000
                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-21 10:14 -0500
                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 19:09 +0200
                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Dan Espen <dan1espen@gmail.com> - 2019-06-21 13:39 -0400
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 19:07 +0200
                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "F. Russell" <frussell@random.info> - 2019-06-21 17:19 +0000
                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 19:57 +0200
                                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "F. Russell" <fr@random.info> - 2019-06-21 23:14 +0000
                                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Lucifer <LuciferMorningstar@bigpond.com> - 2019-06-23 19:00 +1000
                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug RonB <ronb02NOSPAM@gmail.com> - 2019-06-22 00:17 +0000
                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2019-06-22 02:08 -0400
                                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E. R." <robin_listas@es.invalid> - 2019-06-23 12:59 +0200
                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Dan Espen <dan1espen@gmail.com> - 2019-06-21 11:18 -0400
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 19:10 +0200
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-21 19:57 +0000
                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 23:09 +0200
                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-06-21 08:17 +0100
                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 13:03 +0200
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-19 19:51 +0000
                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 22:45 +0200
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug ruben safir <ruben@mrbrklyn.com> - 2019-07-20 19:46 -0400
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 21:00 +0200
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-06-19 20:20 +0100
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 14:43 +0200
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-19 16:44 -0400
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 22:57 +0200
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Wildman <best_lay@yahoo.com> - 2019-06-19 16:17 -0500
                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-19 17:43 -0400
                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 00:58 +0200
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-19 17:40 -0400
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-19 23:53 +0200
          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug ruben safir <ruben@mrbrklyn.com> - 2019-07-20 19:31 -0400
    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Freenet" <pieer@free.fr> - 2019-06-16 20:44 -0500
      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Jasen Betts <jasen@xnet.co.nz> - 2019-06-17 12:41 +0000
        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-17 17:30 -0400
          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-18 11:29 +0200
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-18 16:15 -0400
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-18 20:28 +0000
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-18 17:27 -0400
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-19 00:04 +0000
                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-18 22:36 -0400
                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 10:06 +0200
                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-19 16:15 -0400
                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 14:51 +0200
                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Aragorn <thorongil@telenet.be> - 2019-06-20 15:13 +0200
                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 19:14 +0200
                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-20 12:21 -0600
                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Roger Blake <rogblake@iname.invalid> - 2019-06-21 00:56 +0000
                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-20 16:07 -0400
                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-20 14:24 -0600
                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-20 16:51 -0400
                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 23:02 +0200
                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-20 15:14 -0600
                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 13:41 +0200
                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> - 2019-06-21 09:30 -0500
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 19:14 +0200
                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-21 12:34 -0600
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 23:53 +0200
                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 22:55 +0200
                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-20 15:17 -0600
                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 14:03 +0200
                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-21 22:59 -0600
                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-22 07:51 -0500
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-22 16:53 -0600
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-22 18:56 -0500
                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-22 20:09 -0600
                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-22 22:48 -0500
                                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-22 22:51 -0600
                                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E. R." <robin_listas@es.invalid> - 2019-06-23 13:19 +0200
                                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-23 07:33 -0500
                                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-06-23 15:07 +0100
                                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E. R." <robin_listas@es.invalid> - 2019-06-24 02:09 +0200
                                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-23 22:22 -0500
                                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E. R." <robin_listas@es.invalid> - 2019-06-24 11:41 +0200
                                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-24 07:24 -0500
                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E. R." <robin_listas@es.invalid> - 2019-06-23 13:14 +0200
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-23 11:50 -0600
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E. R." <robin_listas@es.invalid> - 2019-06-24 02:41 +0200
                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-30 15:08 -0600
                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Melzzzzz <Melzzzzz@zzzzz.com> - 2019-06-30 21:14 +0000
                                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-30 15:22 -0600
                                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Melzzzzz <Melzzzzz@zzzzz.com> - 2019-06-30 21:47 +0000
                                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Jasen Betts <jasen@xnet.co.nz> - 2019-07-01 08:10 +0000
                                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-07-01 10:05 +0100
                                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-07-01 12:54 +0200
                                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-07-01 12:08 +0100
                                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Jasen Betts <jasen@xnet.co.nz> - 2019-07-01 11:54 +0000
                                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Paul <nospam@needed.invalid> - 2019-07-01 12:30 -0400
                                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-07-01 17:11 -0600
                                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-07-01 17:06 -0600
                                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Jasen Betts <jasen@xnet.co.nz> - 2019-07-02 09:35 +0000
                                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-07-02 09:20 -0600
                                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-07-02 14:28 +0200
                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Jasen Betts <jasen@xnet.co.nz> - 2019-07-01 07:51 +0000
                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-07-01 12:46 +0200
                                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-07-01 09:50 -0500
                                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-07-01 17:31 +0200
                                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-07-01 12:10 -0500
                                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-07-02 14:17 +0200
                                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-07-02 10:22 -0500
                                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-07-02 19:10 +0200
                                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-07-02 19:16 +0200
                                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-07-02 12:27 -0600
                                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-07-02 14:33 -0500
                                                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-07-03 13:34 +0200
                                                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-07-03 09:06 -0500
                                                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-07-04 03:14 +0100
                                                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug - spam on mail "Carlos E.R." <robin_listas@es.invalid> - 2019-07-04 15:26 +0200
                                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-07-01 17:16 -0600
                                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-07-02 14:20 +0200
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-23 16:36 -0400
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E. R." <robin_listas@es.invalid> - 2019-06-24 03:37 +0200
                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-24 13:50 -0400
                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-24 23:14 +0200
                                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-21 16:01 -0400
                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 23:57 +0200
                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-21 17:35 -0500
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> - 2019-06-21 22:04 -0500
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-22 12:57 -0400
                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> - 2019-06-21 21:58 -0500
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-22 07:32 -0500
                                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-21 23:10 -0600
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-06-22 08:21 +0100
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-22 13:01 -0400
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-22 16:55 -0600
                                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug John Hasler <jhasler@newsguy.com> - 2019-06-22 18:47 -0500
                                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-22 20:15 -0600
                                        Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] "Carlos E. R." <robin_listas@es.invalid> - 2019-06-23 13:52 +0200
                                          Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] John Hasler <jhasler@newsguy.com> - 2019-06-23 10:02 -0500
                                            Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] "Carlos E. R." <robin_listas@es.invalid> - 2019-06-24 02:17 +0200
                                              Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] John Hasler <jhasler@newsguy.com> - 2019-06-23 22:30 -0500
                                          Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-23 11:56 -0600
                                            Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] Sidney_Kotic <kant@have.it> - 2019-06-23 10:11 -0800
                                            Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] "Carlos E. R." <robin_listas@es.invalid> - 2019-06-24 03:23 +0200
                                              Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] Jasen Betts <jasen@xnet.co.nz> - 2019-06-24 09:07 +0000
                                                Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] "Carlos E. R." <robin_listas@es.invalid> - 2019-06-24 11:52 +0200
                                                  Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] Andreas Kohlbach <ank@spamfence.net> - 2019-06-24 14:14 -0400
                                                    Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] "Carlos E.R." <robin_listas@es.invalid> - 2019-06-24 23:21 +0200
                                              Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-30 15:38 -0600
                                          Re: Ancient networking [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-30 15:31 -0600
                                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Bud Frede <frede@mouse-potato.com> - 2019-06-30 09:17 -0400
                                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-30 15:41 -0600
                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-21 23:02 -0600
                                      Fidonet [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] "Carlos E. R." <robin_listas@es.invalid> - 2019-06-23 14:02 +0200
                                        Re: Fidonet [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] Jasen Betts <jasen@xnet.co.nz> - 2019-06-24 09:11 +0000
                                          Re: Fidonet [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] "Carlos E. R." <robin_listas@es.invalid> - 2019-06-24 11:53 +0200
                                        Re: Fidonet [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] Steve Hayes <hayesstw@telkomsa.net> - 2019-06-25 07:37 +0200
                                          Re: Fidonet [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] "Carlos E.R." <robin_listas@es.invalid> - 2019-06-25 16:49 +0200
                                            Re: Fidonet [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] The Natural Philosopher <tnp@invalid.invalid> - 2019-06-25 19:34 +0100
                                          Re: Fidonet [Was: Re: Linux Command-Line Editors Vulnerable to High-Severity Bug] Bud Frede <frede@mouse-potato.com> - 2019-06-30 09:36 -0400
                                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Bud Frede <frede@mouse-potato.com> - 2019-06-30 08:52 -0400
                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Bud Frede <frede@mouse-potato.com> - 2019-06-30 08:25 -0400
                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-30 20:01 +0200
                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug The Natural Philosopher <tnp@invalid.invalid> - 2019-06-30 20:57 +0100
                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-30 15:47 -0600
                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Jean-David Beyer <jeandavid8@verizon.net> - 2019-06-30 16:13 -0400
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 00:43 +0200
          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 10:28 +0200
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Rich <rich@example.invalid> - 2019-06-19 10:30 +0000
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 12:51 +0200
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Rich <rich@example.invalid> - 2019-06-19 11:30 +0000
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 21:03 +0200
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-19 12:30 +0000
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 21:11 +0200
                    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-19 20:10 +0000
                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-19 22:18 +0200
                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-19 20:33 +0000
                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 23:05 +0200
                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-19 23:30 +0000
                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-19 21:43 -0600
                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-20 05:50 +0200
                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 23:20 +0200
                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Dan Espen <dan1espen@gmail.com> - 2019-06-19 21:45 -0400
                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-20 03:23 +0000
                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Grant Taylor <gtaylor@tnetconsulting.net> - 2019-06-19 21:45 -0600
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 23:15 +0200
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Bud Frede <frede@mouse-potato.com> - 2019-06-30 09:54 -0400
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-30 20:06 +0200
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug DecadentLinuxUserNumeroUno@decadence.org - 2019-06-19 11:55 +0000
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug DecadentLinuxUserNumeroUno@decadence.org - 2019-06-22 13:20 +0000
    Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Anonymous <nobody@remailer.paranoici.org> - 2019-06-25 15:11 +0200

Page 12 of 13 — ← Prev page 1 … 10 11 [12] 13  Next page →

#56979

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 10:28 +0200
Message-ID<0a8ptf-ogu.ln1@Telcontar.valinor>
In reply to#56953
On 18/06/2019 01.22, owl wrote:
> In comp.os.linux.advocacy Andreas Kohlbach <ank@spamfence.net> wrote:
>> On Mon, 17 Jun 2019 12:41:08 -0000 (UTC), Jasen Betts wrote:
>>>
>>> On 2019-06-17, Freenet <pieer@free.fr> wrote:
>>>>>
>>>>> (I have never understood why anyone would want to waste their time
>>>>> learning how to use that Vim crap.  Just a foolish venture into
>>>>> egotistical intellectual chauvinism.)
>>>>
>>>>   What I hate about it is when I accidentally start it.  I then
>>>> usually have to go and dig around the web to find out how to close
>>>> it.
>>>
>>> indeed that is the one essential vi skill <Esc> : q ! <Enter>
>>
>> And that information is missing in the "splash screen" (displayed when
>> you open vi without a file name). This Red Button should IMO be mentioned.
>>
> 
> It's not missing from the splash in vim.

I get no splash. Never did.

> 
> "               type  :q<Enter>               to exit"                         
> 
> If you have made edits and try to quit with :q, you get
> 
> "E37: No write since last change (add ! to override)"
> 
> Seems clear enough to me.  If not, you can always type
> :help quit

For which you have to know that you have to type that cryptic command!
Why not F1, the universal Help key?  Or control-H.

I tried now that ":help", and took me a minute to manage to exit help.

j for going down a line? Gosh, keyboards have down keys for decades!

> or hit F1, where brief instructions for quiting are just
> a few lines in.

Nope, I get a window asking if I want the XFCE terminal help.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#56981

FromRich <rich@example.invalid>
Date2019-06-19 10:30 +0000
Message-ID<qed2rv$jos$1@dont-email.me>
In reply to#56979
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
> j for going down a line?  Gosh, keyboards have down keys for decades!

Yes, but if you go back enough decades (1976) they did not:

https://en.wikipedia.org/wiki/ADM-3A#Hardware

Notice what is also printed on the h, j, k, and l keys in the keyboard 
layout at that URL.

[toc] | [prev] | [next] | [standalone]

#56983

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 12:51 +0200
Message-ID<7mgptf-cg4.ln1@Telcontar.valinor>
In reply to#56981
On 19/06/2019 12.30, Rich wrote:
> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>> j for going down a line?  Gosh, keyboards have down keys for decades!
> 
> Yes, but if you go back enough decades (1976) they did not:
> 
> https://en.wikipedia.org/wiki/ADM-3A#Hardware
> 
> Notice what is also printed on the h, j, k, and l keys in the keyboard 
> layout at that URL.

So? This is 2019.


       er
ctrl asdf
       xc

were the equivalent keys in wordstar, and they still work in joe. Not
that I ever use them, even if I remember them. Time enough to change.

(and wordstar was designed for typists, very widely used by people whose
profession was typing stuff)


That the vi help today shows the h j k l keys in its main page shows its
age and obsolescence. Enough to having me running away - and I'm old
enough to having seen it, but the first keyboard I bought around 1984
had arrows. Verified in my personal museum just now.


Don't take me wrong, I know that vi is a very powerful editor. But
boasting of the h j k l is enough to send me running away from it again.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#56986

FromRich <rich@example.invalid>
Date2019-06-19 11:30 +0000
Message-ID<qed6ci$6d0$2@dont-email.me>
In reply to#56983
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
> On 19/06/2019 12.30, Rich wrote:
>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>> j for going down a line?  Gosh, keyboards have down keys for decades!
>> 
>> Yes, but if you go back enough decades (1976) they did not:
>> 
>> https://en.wikipedia.org/wiki/ADM-3A#Hardware
>> 
>> Notice what is also printed on the h, j, k, and l keys in the keyboard 
>> layout at that URL.
> 
> So? This is 2019.
> 
> 
>       er
> ctrl asdf
>       xc
> 
> were the equivalent keys in wordstar, and they still work in joe. Not
> that I ever use them, even if I remember them. Time enough to change.
> 
> (and wordstar was designed for typists, very widely used by people whose
> profession was typing stuff)
> 
> 
> That the vi help today shows the h j k l keys in its main page shows its
> age and obsolescence. Enough to having me running away - and I'm old
> enough to having seen it, but the first keyboard I bought around 1984
> had arrows. Verified in my personal museum just now.
> 
> 
> Don't take me wrong, I know that vi is a very powerful editor. But
> boasting of the h j k l is enough to send me running away from it again.

Wasn't a boast.  That keyboard was where the mapping of hjkl to up, 
down, left, and right derived from.  Vi was written on that terminal 
(according to the history).  That was where the choice of that, very 
odd seeming today with every keyboard having dedicated cursor keys, 
mapping came from.

At the time, the mapping made sense, and any new users using that 
terminal and keyboard would have had printed key caps that told them 
what to press.

Today, without the printed arrows on modern keyboards, yes the mapping 
seems strange and arbitrary, and completly non-discoverable to a new 
user.

[toc] | [prev] | [next] | [standalone]

#56994

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 21:03 +0200
Message-ID<khdqtf-7ho.ln1@Telcontar.valinor>
In reply to#56986
On 19/06/2019 13.30, Rich wrote:
> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 19/06/2019 12.30, Rich wrote:
>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>>> j for going down a line?  Gosh, keyboards have down keys for decades!
>>>
>>> Yes, but if you go back enough decades (1976) they did not:
>>>
>>> https://en.wikipedia.org/wiki/ADM-3A#Hardware
>>>
>>> Notice what is also printed on the h, j, k, and l keys in the keyboard 
>>> layout at that URL.
>>
>> So? This is 2019.
>>
>>
>>       er
>> ctrl asdf
>>       xc
>>
>> were the equivalent keys in wordstar, and they still work in joe. Not
>> that I ever use them, even if I remember them. Time enough to change.
>>
>> (and wordstar was designed for typists, very widely used by people whose
>> profession was typing stuff)
>>
>>
>> That the vi help today shows the h j k l keys in its main page shows its
>> age and obsolescence. Enough to having me running away - and I'm old
>> enough to having seen it, but the first keyboard I bought around 1984
>> had arrows. Verified in my personal museum just now.
>>
>>
>> Don't take me wrong, I know that vi is a very powerful editor. But
>> boasting of the h j k l is enough to send me running away from it again.
> 
> Wasn't a boast.  That keyboard was where the mapping of hjkl to up, 
> down, left, and right derived from.  Vi was written on that terminal 
> (according to the history).  That was where the choice of that, very 
> odd seeming today with every keyboard having dedicated cursor keys, 
> mapping came from.
> 
> At the time, the mapping made sense, and any new users using that 
> terminal and keyboard would have had printed key caps that told them 
> what to press.
> 
> Today, without the printed arrows on modern keyboards, yes the mapping 
> seems strange and arbitrary, and completly non-discoverable to a new 
> user.

I know that the mapping is there. What I say is that it is irrelevant
and should be hidden in the depth of an info file, not on the first screen.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#56988

Fromowl <owl@rooftop.invalid>
Date2019-06-19 12:30 +0000
Message-ID<ghiz003.agp5au@rooftop.invalid>
In reply to#56983
In alt.os.linux Carlos E.R. <robin_listas@es.invalid> wrote:
> On 19/06/2019 12.30, Rich wrote:
>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>> j for going down a line?  Gosh, keyboards have down keys for decades!
>> 
>> Yes, but if you go back enough decades (1976) they did not:
>> 
>> https://en.wikipedia.org/wiki/ADM-3A#Hardware
>> 
>> Notice what is also printed on the h, j, k, and l keys in the keyboard 
>> layout at that URL.
> 
> So? This is 2019.
> 
> 
>        er
> ctrl asdf
>        xc
> 
> were the equivalent keys in wordstar, and they still work in joe. Not
> that I ever use them, even if I remember them. Time enough to change.
> 
> (and wordstar was designed for typists, very widely used by people whose
> profession was typing stuff)
> 
> 
> That the vi help today shows the h j k l keys in its main page shows its
> age and obsolescence. Enough to having me running away - and I'm old
> enough to having seen it, but the first keyboard I bought around 1984
> had arrows. Verified in my personal museum just now.
> 

My first keyboard was a typewriter in 1975.  Not one of those newfangled
electric ones either.  A real man's typewriter that required a strong
pounding of the keys and a swipe of the hand for a carriage return. :)

> 
> Don't take me wrong, I know that vi is a very powerful editor. But
> boasting of the h j k l is enough to send me running away from it again.
> 

The hjkl navigation is more efficient than the arrows, since it doesn't
require that you either make an awkward pinky reach or possibly move
your hand from the home row.  But even given that, the h and l are
better reserved for character navigation within a word, since w and b
(forward and backward by word) are otherise more efficent.  But the real
power of vim navigation comes from the fact that these commands can be
given a count.  For example, 20j or 20k to go down or up by twenty lines.
Then there are '(' and ')' for sentence navigation, and '{' and '}' for
paragraph navigation.   And let's not forget gj and gk for navigating down
and up by visible line in a word-wrapped block.  And all of these can
be given a count as well.  And jumping to line N with :N.  And marking
locations with 'm'.  And passing a range of lines to the fmt cmd with
:12,20!fmt.  It just gets better and better the more you use it. :)

[toc] | [prev] | [next] | [standalone]

#56995

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 21:11 +0200
Message-ID<10eqtf-scp.ln1@Telcontar.valinor>
In reply to#56988
On 19/06/2019 14.30, owl wrote:
> In alt.os.linux Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 19/06/2019 12.30, Rich wrote:
>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>>> j for going down a line?  Gosh, keyboards have down keys for decades!
>>>
>>> Yes, but if you go back enough decades (1976) they did not:
>>>
>>> https://en.wikipedia.org/wiki/ADM-3A#Hardware
>>>
>>> Notice what is also printed on the h, j, k, and l keys in the keyboard 
>>> layout at that URL.
>>
>> So? This is 2019.
>>
>>
>>        er
>> ctrl asdf
>>        xc
>>
>> were the equivalent keys in wordstar, and they still work in joe. Not
>> that I ever use them, even if I remember them. Time enough to change.
>>
>> (and wordstar was designed for typists, very widely used by people whose
>> profession was typing stuff)
>>
>>
>> That the vi help today shows the h j k l keys in its main page shows its
>> age and obsolescence. Enough to having me running away - and I'm old
>> enough to having seen it, but the first keyboard I bought around 1984
>> had arrows. Verified in my personal museum just now.
>>
> 
> My first keyboard was a typewriter in 1975.  Not one of those newfangled
> electric ones either.  A real man's typewriter that required a strong
> pounding of the keys and a swipe of the hand for a carriage return. :)

Same here. And I'll bet you that mine was harder, being an ancient model
from 1920 perhaps. Till my father asked a friend to get us (his son and
me) a modern typewriter each from abroad (also mechanical, electric was
prohibitive). Contraband, probably.



>> Don't take me wrong, I know that vi is a very powerful editor. But
>> boasting of the h j k l is enough to send me running away from it again.
>>
> 
> The hjkl navigation is more efficient than the arrows, since it doesn't
> require that you either make an awkward pinky reach or possibly move
> your hand from the home row.  But even given that, the h and l are
> better reserved for character navigation within a word, since w and b
> (forward and backward by word) are otherise more efficent.  

Yeah, sure :-P

> But the real
> power of vim navigation comes from the fact that these commands can be
> given a count.  For example, 20j or 20k to go down or up by twenty lines.

Yes, I have seen that on some ancient editors. I can live without it :-)

> Then there are '(' and ')' for sentence navigation, and '{' and '}' for
> paragraph navigation.   And let's not forget gj and gk for navigating down
> and up by visible line in a word-wrapped block.  And all of these can
> be given a count as well.  And jumping to line N with :N.  And marking
> locations with 'm'.  And passing a range of lines to the fmt cmd with
> :12,20!fmt.  It just gets better and better the more you use it. :)

Those have an use, agreed.

But other editors would do similar things with ctrl-arrows, for instance.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#57000

Fromowl <owl@rooftop.invalid>
Date2019-06-19 20:10 +0000
Message-ID<y7820qr.qh3@rooftop.invalid>
In reply to#56995
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
> On 19/06/2019 14.30, owl wrote:
>> In alt.os.linux Carlos E.R. <robin_listas@es.invalid> wrote:
>>> On 19/06/2019 12.30, Rich wrote:
>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>>>> j for going down a line?  Gosh, keyboards have down keys for decades!
>>>>
>>>> Yes, but if you go back enough decades (1976) they did not:
>>>>
>>>> https://en.wikipedia.org/wiki/ADM-3A#Hardware
>>>>
>>>> Notice what is also printed on the h, j, k, and l keys in the keyboard 
>>>> layout at that URL.
>>>
>>> So? This is 2019.
>>>
>>>
>>>        er
>>> ctrl asdf
>>>        xc
>>>
>>> were the equivalent keys in wordstar, and they still work in joe. Not
>>> that I ever use them, even if I remember them. Time enough to change.
>>>
>>> (and wordstar was designed for typists, very widely used by people whose
>>> profession was typing stuff)
>>>
>>>
>>> That the vi help today shows the h j k l keys in its main page shows its
>>> age and obsolescence. Enough to having me running away - and I'm old
>>> enough to having seen it, but the first keyboard I bought around 1984
>>> had arrows. Verified in my personal museum just now.
>>>
>> 
>> My first keyboard was a typewriter in 1975.  Not one of those newfangled
>> electric ones either.  A real man's typewriter that required a strong
>> pounding of the keys and a swipe of the hand for a carriage return. :)
> 
> Same here. And I'll bet you that mine was harder, being an ancient model
> from 1920 perhaps. Till my father asked a friend to get us (his son and
> me) a modern typewriter each from abroad (also mechanical, electric was
> prohibitive). Contraband, probably.
> 

I found an ancient typewriter under the basement stairs in a house we used
to live in.  Then I forgot about it when we moved. :)

> 
> 
>>> Don't take me wrong, I know that vi is a very powerful editor. But
>>> boasting of the h j k l is enough to send me running away from it again.
>>>
>> 
>> The hjkl navigation is more efficient than the arrows, since it doesn't
>> require that you either make an awkward pinky reach or possibly move
>> your hand from the home row.  But even given that, the h and l are
>> better reserved for character navigation within a word, since w and b
>> (forward and backward by word) are otherise more efficent.  
> 
> Yeah, sure :-P
> 

Yep.  '8w' is more efficient than '40l' for a guess at jumping to a word
near the middle of a line, and definitely more efficient than
'llllllllllllllllllllllllllllllllllllllll'

>> But the real
>> power of vim navigation comes from the fact that these commands can be
>> given a count.  For example, 20j or 20k to go down or up by twenty lines.
> 
> Yes, I have seen that on some ancient editors. I can live without it :-)
>

And the alternative is less efficient.
 
>> Then there are '(' and ')' for sentence navigation, and '{' and '}' for
>> paragraph navigation.   And let's not forget gj and gk for navigating down
>> and up by visible line in a word-wrapped block.  And all of these can
>> be given a count as well.  And jumping to line N with :N.  And marking
>> locations with 'm'.  And passing a range of lines to the fmt cmd with
>> :12,20!fmt.  It just gets better and better the more you use it. :)
> 
> Those have an use, agreed.
> 
> But other editors would do similar things with ctrl-arrows, for instance.
> 

Less efficiently.

[toc] | [prev] | [next] | [standalone]

#57002

FromGeorges <georges@prout.com>
Date2019-06-19 22:18 +0200
Message-ID<qee5bh$lf1$1@gioia.aioe.org>
In reply to#57000
Le 19/06/2019 à 22:10, owl a écrit :

snip

>>
> 
> Yep.  '8w' is more efficient than '40l' for a guess at jumping to a word
> near the middle of a line, and definitely more efficient than
> 'llllllllllllllllllllllllllllllllllllllll'
> 

place on the beginning of the word you like
or
/\<word\>

ma (mark a)

navigate thru the file...

'a -> the beginning of the line containing the mark "a"
`a -> the word marked "a"

;)

-- 
()
/\

[toc] | [prev] | [next] | [standalone]

#57003

Fromowl <owl@rooftop.invalid>
Date2019-06-19 20:33 +0000
Message-ID<savd93ra.3@rooftop.invalid>
In reply to#57002
In comp.os.linux.misc Georges <georges@prout.com> wrote:
> Le 19/06/2019 à 22:10, owl a écrit :
> 
> snip
> 
>>>
>> 
>> Yep.  '8w' is more efficient than '40l' for a guess at jumping to a word
>> near the middle of a line, and definitely more efficient than
>> 'llllllllllllllllllllllllllllllllllllllll'
>> 
> 
> place on the beginning of the word you like
> or
> /\<word\>
> 
> ma (mark a)
> 
> navigate thru the file...
> 
> 'a -> the beginning of the line containing the mark "a"
> `a -> the word marked "a"
> 
> ;)
> 

Yes, but I'm talking about general navigation, not finding a particular word,
which even within a sentence would require typing more characters than
just '8w'.  Then you can fine-tune the location if necessary with h and l.

[toc] | [prev] | [next] | [standalone]

#57008

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 23:05 +0200
Message-ID<nlkqtf-g5v.ln1@Telcontar.valinor>
In reply to#57000
On 19/06/2019 22.10, owl wrote:
> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 19/06/2019 14.30, owl wrote:
>>> In alt.os.linux Carlos E.R. <robin_listas@es.invalid> wrote:
>>>> On 19/06/2019 12.30, Rich wrote:
>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>>>>> j for going down a line?  Gosh, keyboards have down keys for decades!
>>>>>
>>>>> Yes, but if you go back enough decades (1976) they did not:
>>>>>
>>>>> https://en.wikipedia.org/wiki/ADM-3A#Hardware
>>>>>
>>>>> Notice what is also printed on the h, j, k, and l keys in the keyboard 
>>>>> layout at that URL.
>>>>
>>>> So? This is 2019.
>>>>
>>>>
>>>>        er
>>>> ctrl asdf
>>>>        xc
>>>>
>>>> were the equivalent keys in wordstar, and they still work in joe. Not
>>>> that I ever use them, even if I remember them. Time enough to change.
>>>>
>>>> (and wordstar was designed for typists, very widely used by people whose
>>>> profession was typing stuff)
>>>>
>>>>
>>>> That the vi help today shows the h j k l keys in its main page shows its
>>>> age and obsolescence. Enough to having me running away - and I'm old
>>>> enough to having seen it, but the first keyboard I bought around 1984
>>>> had arrows. Verified in my personal museum just now.
>>>>
>>>
>>> My first keyboard was a typewriter in 1975.  Not one of those newfangled
>>> electric ones either.  A real man's typewriter that required a strong
>>> pounding of the keys and a swipe of the hand for a carriage return. :)
>>
>> Same here. And I'll bet you that mine was harder, being an ancient model
>> from 1920 perhaps. Till my father asked a friend to get us (his son and
>> me) a modern typewriter each from abroad (also mechanical, electric was
>> prohibitive). Contraband, probably.
>>
> 
> I found an ancient typewriter under the basement stairs in a house we used
> to live in.  Then I forgot about it when we moved. :)
> 
>>
>>
>>>> Don't take me wrong, I know that vi is a very powerful editor. But
>>>> boasting of the h j k l is enough to send me running away from it again.
>>>>
>>>
>>> The hjkl navigation is more efficient than the arrows, since it doesn't
>>> require that you either make an awkward pinky reach or possibly move
>>> your hand from the home row.  But even given that, the h and l are
>>> better reserved for character navigation within a word, since w and b
>>> (forward and backward by word) are otherise more efficent.  
>>
>> Yeah, sure :-P
>>
> 
> Yep.  '8w' is more efficient than '40l' for a guess at jumping to a word
> near the middle of a line, and definitely more efficient than
> 'llllllllllllllllllllllllllllllllllllllll'
> 
>>> But the real
>>> power of vim navigation comes from the fact that these commands can be
>>> given a count.  For example, 20j or 20k to go down or up by twenty lines.
>>
>> Yes, I have seen that on some ancient editors. I can live without it :-)
>>
> 
> And the alternative is less efficient.

Sure, when you already know that it is 20 chars or 20 words in one
direction. I never know, I would have to count them. If I see the point,
I click the mouse at it.

Yes, I have used that command to move so many letters or words to the
right. I think it was on a VAX computer running, what, VMS? The machine
was so loaded with student assignments, that it would obey the cursor
perhaps after 5 or 30 seconds. So to correct a typo that made the
compile fail, we counted lines and words and typed the correction
blindly. Then cross the fingers waiting to be "executed" in an instant
to find out the result.

As I say, ancient ages. I don't have to do that now.

>  
>>> Then there are '(' and ')' for sentence navigation, and '{' and '}' for
>>> paragraph navigation.   And let's not forget gj and gk for navigating down
>>> and up by visible line in a word-wrapped block.  And all of these can
>>> be given a count as well.  And jumping to line N with :N.  And marking
>>> locations with 'm'.  And passing a range of lines to the fmt cmd with
>>> :12,20!fmt.  It just gets better and better the more you use it. :)
>>
>> Those have an use, agreed.
>>
>> But other editors would do similar things with ctrl-arrows, for instance.
>>
> 
> Less efficiently.

Maybe, maybe not. There is a learning effort involved, too. I'm not
going to invest it :-)

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#57015

Fromowl <owl@rooftop.invalid>
Date2019-06-19 23:30 +0000
Message-ID<guzbv30ga.h4@rooftop.invalid>
In reply to#57008
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
> On 19/06/2019 22.10, owl wrote:
>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>> On 19/06/2019 14.30, owl wrote:
>>>> But the real
>>>> power of vim navigation comes from the fact that these commands can be
>>>> given a count.  For example, 20j or 20k to go down or up by twenty lines.
>>>
>>> Yes, I have seen that on some ancient editors. I can live without it :-)
>>>
>> 
>> And the alternative is less efficient.
> 
> Sure, when you already know that it is 20 chars or 20 words in one
> direction. I never know, I would have to count them. If I see the point,
> I click the mouse at it.
> 

Sometimes mouse-click placement is inaccurate.  Very often for me, in
fact, unless I do it slowly.  And there is the very need to reach for
the mouse in the first place.  With vim, you can get the cursor exactly
where you need it in three or four rapid keystrokes.

[toc] | [prev] | [next] | [standalone]

#57019

FromGrant Taylor <gtaylor@tnetconsulting.net>
Date2019-06-19 21:43 -0600
Message-ID<qeevf1$npv$1@tncsrv09.home.tnetconsulting.net>
In reply to#57015
On 6/19/19 5:30 PM, owl wrote:
> Sometimes mouse-click placement is inaccurate.  Very often for me, 
> in fact, unless I do it slowly.  And there is the very need to reach 
> for the mouse in the first place.  With vim, you can get the cursor 
> exactly where you need it in three or four rapid keystrokes.

Especially if those keystrokes are searches.

t or T or f or F or ? or /

Especially if you combine them with other actions, like c for change, or 
d for delete.

There are a LOT of different things that can be done.  }:-)

Vim, takes less than an your to learn the basics, but a lifetime to master.



-- 
Grant. . . .
unix || die

[toc] | [prev] | [next] | [standalone]

#57021

FromGeorges <georges@prout.com>
Date2019-06-20 05:50 +0200
Message-ID<qeevr1$45g$1@gioia.aioe.org>
In reply to#57019
Le 20/06/2019 à 05:43, Grant Taylor a écrit :

snip

> 
> Vim, takes less than an hour to learn the basics, but a lifetime to master.
> 

Yes... for sure !
;)

-- 
()
/\

[toc] | [prev] | [next] | [standalone]

#57052

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-20 23:20 +0200
Message-ID<5t9ttf-f1r.ln1@Telcontar.valinor>
In reply to#57015
On 20/06/2019 06.23, Charlie Gibbs wrote:
> On 2019-06-19, owl <owl@rooftop.invalid> wrote:
> 
>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>
>>> On 19/06/2019 22.10, owl wrote:
>>>
>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>>>
>>>>> On 19/06/2019 14.30, owl wrote:
>>>>>
>>>>>> But the real
>>>>>> power of vim navigation comes from the fact that these commands can be
>>>>>> given a count.  For example, 20j or 20k to go down or up by twenty lines.
>>>>>
>>>>> Yes, I have seen that on some ancient editors. I can live without it :-)
>>>>
>>>> And the alternative is less efficient.
>>>
>>> Sure, when you already know that it is 20 chars or 20 words in one
>>> direction. I never know, I would have to count them. If I see the point,
>>> I click the mouse at it.
>>
>> Sometimes mouse-click placement is inaccurate.  Very often for me, in
>> fact, unless I do it slowly.
> 
> Few people realize the tremendous demands made on hand/eye co-ordination
> by a mouse as opposed to a keyboard - until they click on the wrong thing
> and have to spend a lot of time undoing the mess that results.

ctrl-z, undo.

>  But they
> soon forget... the screen is so shiny...
> 
>> And there is the very need to reach for the mouse in the first place.
>> With vim, you can get the cursor exactly where you need it in three or
>> four rapid keystrokes.
> 
> For me, one mouse click requires the same time and effort as about
> 10 keystrokes.  It's little wonder that I quickly learn keyboard
> shortcuts - and become quite incensed when they aren't available.
> 


-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#57016

FromDan Espen <dan1espen@gmail.com>
Date2019-06-19 21:45 -0400
Message-ID<qeeof9$qbr$1@dont-email.me>
In reply to#57000
owl <owl@rooftop.invalid> writes:

> Yep.  '8w' is more efficient than '40l' for a guess at jumping to a word
> near the middle of a line, and definitely more efficient than
> 'llllllllllllllllllllllllllllllllllllllll'

Actually, all those "l"s are one keystroke.
Assuming you've let your keyboard do auto-repeat.
Looks like 1 keystroke vs 2 or 3.

-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]

#57018

Fromowl <owl@rooftop.invalid>
Date2019-06-20 03:23 +0000
Message-ID<suz7993g.vgui4@rooftop.invalid>
In reply to#57016
In comp.os.linux.misc Dan Espen <dan1espen@gmail.com> wrote:
> owl <owl@rooftop.invalid> writes:
> 
>> Yep.  '8w' is more efficient than '40l' for a guess at jumping to a word
>> near the middle of a line, and definitely more efficient than
>> 'llllllllllllllllllllllllllllllllllllllll'
> 
> Actually, all those "l"s are one keystroke.
> Assuming you've let your keyboard do auto-repeat.
> Looks like 1 keystroke vs 2 or 3.
> 

A 1.5-second keystroke.  No thanks.

[toc] | [prev] | [next] | [standalone]

#57020

FromGrant Taylor <gtaylor@tnetconsulting.net>
Date2019-06-19 21:45 -0600
Message-ID<qeevh7$npv$2@tncsrv09.home.tnetconsulting.net>
In reply to#57016
On 6/19/19 7:45 PM, Dan Espen wrote:
> Actually, all those "l"s are one keystroke.
> Assuming you've let your keyboard do auto-repeat.

~shudder~ the thought of waiting on a keyboard auto-repeat for a large 
number of letters.  Not to mention keeping track of them and not over or 
under shooting.



-- 
Grant. . . .
unix || die

[toc] | [prev] | [next] | [standalone]

#57050

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-20 23:15 +0200
Message-ID<lk9ttf-f1r.ln1@Telcontar.valinor>
In reply to#56988
On 19/06/2019 20.23, Charlie Gibbs wrote:
> On 2019-06-19, owl <owl@rooftop.invalid> wrote:
> 
>> In alt.os.linux Carlos E.R. <robin_listas@es.invalid> wrote:
>>
>>> That the vi help today shows the h j k l keys in its main page shows its
>>> age and obsolescence. Enough to having me running away - and I'm old
>>> enough to having seen it, but the first keyboard I bought around 1984
>>> had arrows. Verified in my personal museum just now.
>>
>> My first keyboard was a typewriter in 1975.  Not one of those newfangled
>> electric ones either.  A real man's typewriter that required a strong
>> pounding of the keys and a swipe of the hand for a carriage return. :)
> 
> Been there, done that (although about 15 years earlier).  I always hated
> the letter P, because of how hard my right pinky had to work to make it
> come out clearly.

I remember that.

> 
>>> Don't take me wrong, I know that vi is a very powerful editor. But
>>> boasting of the h j k l is enough to send me running away from it again.
> 
> Ironically, I bet a lot of the people who would shy away from vi's hjkl
> play computer games and have no problem with w (forward), s (back),
> a (left), and d (right).  (I think of "w" as meaning "walk".) In fact,
> some gaming keyboards even have those keys in a different colour.

Because that was the standard keyboard, not vi's :-p

Admittedly, some have that in order to accommodate two players on the
same keyboard.

> 
>> The hjkl navigation is more efficient than the arrows, since it doesn't
>> require that you either make an awkward pinky reach or possibly move
>> your hand from the home row.  But even given that, the h and l are
>> better reserved for character navigation within a word, since w and b
>> (forward and backward by word) are otherise more efficent.  But the real
>> power of vim navigation comes from the fact that these commands can be
>> given a count.  For example, 20j or 20k to go down or up by twenty lines.
> 
> Or 3dw to delete three words.
> 
>> Then there are '(' and ')' for sentence navigation, and '{' and '}' for
>> paragraph navigation.   And let's not forget gj and gk for navigating down
>> and up by visible line in a word-wrapped block.  And all of these can
>> be given a count as well.  And jumping to line N with :N.  And marking
>> locations with 'm'.  And passing a range of lines to the fmt cmd with
>> :12,20!fmt.  It just gets better and better the more you use it. :)
> 
> A lot of those are tricks I haven't gotten around to learning yet.
> My favourite newly-learned trick is "/\<word\>", to search for "word"
> without stopping on strings containing "word".  It's a great way to
> look for variables like "i" without getting hundreds of false hits.

Well, I am used to ctrl-[ to find the start/end of brackets. Useful when
coding.


> Another of my favourite tricks is to put the cursor on a brace,
> parenthesis, or bracket and hit "%" to jump to the paired one.
> 
> Then there's "ddp", which swaps the current line with the one below it.
> 
> So much modern software seems to be designed to continually force
> people's hands off the keyboard in favour of the mouse.  The hjkl
> usage means you don't even have to move out of home position to
> hit arrow keys (although I do appreciate having them as an option).
> But then, most users are hunt-and-peck typists who have no idea
> what we're talking about...

There is that. But I'm also a touch typist used to another set of
commands, those of WordStar or Borland, just not those of vi.


-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#57334

FromBud Frede <frede@mouse-potato.com>
Date2019-06-30 09:54 -0400
Message-ID<0audnZ-v-YuwIoXAnZ2dnUU7-TfNnZ2d@supernews.com>
In reply to#56983
"Carlos E.R." <robin_listas@es.invalid> writes:

> On 19/06/2019 12.30, Rich wrote:
>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>> j for going down a line?  Gosh, keyboards have down keys for decades!
>> 
>> Yes, but if you go back enough decades (1976) they did not:
>> 
>> https://en.wikipedia.org/wiki/ADM-3A#Hardware
>> 
>> Notice what is also printed on the h, j, k, and l keys in the keyboard 
>> layout at that URL.
>
> So? This is 2019.

In 2019 I still find it advantageous to use the hjkl keys to navigate
rather than taking my hand off the home row to press the arrow keys.

>
>
>        er
> ctrl asdf
>        xc
>
> were the equivalent keys in wordstar, and they still work in joe. Not
> that I ever use them, even if I remember them. Time enough to change.
>
> (and wordstar was designed for typists, very widely used by people whose
> profession was typing stuff)
>
>
> That the vi help today shows the h j k l keys in its main page shows its
> age and obsolescence. Enough to having me running away - and I'm old
> enough to having seen it, but the first keyboard I bought around 1984
> had arrows. Verified in my personal museum just now.

I know people who still use the wordstar key commands they learned back
when they were using DOS. (One of them uses Joe as "jstar")

I still use vi (vim) and don't find it to be
obsolete. (It's viejo, but not gastado) :-)

It may not be to your tastes or may not fit your needs, but it does work
well for a lot of people and is hardly obsolete.

[toc] | [prev] | [next] | [standalone]

Page 12 of 13 — ← Prev page 1 … 10 11 [12] 13  Next page →

Back to top | Article view | alt.os.linux

csiph-web