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

Groups > comp.os.linux.misc > #27185 > 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 275 — 44 participants

Back to article view | Back to comp.os.linux.misc

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 The Natural Philosopher <tnp@invalid.invalid> - 2019-06-18 14:13 +0100
        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 Georges <georges@prout.com> - 2019-06-17 23:11 +0200
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-17 17:36 -0400
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Dan Espen <dan1espen@gmail.com> - 2019-06-17 18:27 -0400
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-18 08:45 +0200
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2019-06-18 23:58 +0000
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Dan Espen <dan1espen@gmail.com> - 2019-06-18 21:42 -0400
                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2019-06-19 18:23 +0000
                  Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 23:06 +0200
              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug rlhamil@bigapple.pri (Richard L. Hamilton) - 2019-06-22 01:00 +0000
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Richard Kettlewell <invalid@invalid.invalid> - 2019-06-19 07:49 +0100
            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) Shehu Dikko <unreachable@destination.invalid> - 2019-06-20 17:30 +0100
                      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 Kara M'bola <maxupixu@in.val.it> - 2019-06-18 20:12 +0000
    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) Georges <georges@prout.com> - 2019-06-16 22:52 +0200
          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 Georges <georges@prout.com> - 2019-06-16 22:47 +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 Georges <georges@prout.com> - 2019-06-16 22:58 +0200
          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 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 Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2019-06-20 02:15 +0000
                    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 owl <owl@rooftop.invalid> - 2019-06-17 23:22 +0000
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Andreas Kohlbach <ank@spamfence.net> - 2019-06-18 16:07 -0400
            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 Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2019-06-19 18:23 +0000
                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-19 20:42 +0200
                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-19 19:49 +0000
                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-19 21:56 +0200
                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug owl <owl@rooftop.invalid> - 2019-06-19 20:38 +0000
                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-20 00:04 +0200
                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Eric Pozharski <whynot@pozharski.name> - 2019-06-20 11:34 +0300
                      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 "Carlos E.R." <robin_listas@es.invalid> - 2019-06-19 21:11 +0200
                      Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Kara M'bola <maxupixu@in.val.it> - 2019-06-19 19:31 +0000
                        Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-20 23:18 +0200
                          Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Kara M'bola <maxupixu@in.val.it> - 2019-06-21 13:13 +0000
                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug "Carlos E.R." <robin_listas@es.invalid> - 2019-06-22 16:57 +0200
                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Kara M'bola <maxupixu@in.val.it> - 2019-06-23 09:46 +0000
                      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 Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2019-06-20 04:23 +0000
                              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 Kara M'bola <maxupixu@in.val.it> - 2019-06-20 04:49 +0000
                            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-20 07:05 +0200
                              Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Kara M'bola <maxupixu@in.val.it> - 2019-06-20 08:41 +0000
                                Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-20 12:21 +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 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 "Carlos E.R." <robin_listas@es.invalid> - 2019-06-18 03:22 +0200
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Sidney_Kotic <kant@have.it> - 2019-06-17 18:25 -0800
            Re: Linux Command-Line Editors Vulnerable to High-Severity Bug Georges <georges@prout.com> - 2019-06-18 08:30 +0200
            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] "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] Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2019-06-25 17:53 +0000
                                            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 Anonymous <nobody@remailer.paranoici.org> - 2019-06-25 15:11 +0200

Page 6 of 14 — ← Prev page 1 … 4 5 [6] 7 8 … 14  Next page →

#27303

FromCharlie Gibbs <cgibbs@kltpzyxm.invalid>
Date2019-06-20 02:15 +0000
Message-ID<qeeq8v0k2p@news1.newsguy.com>
In reply to#27294
On 2019-06-19, Wildman <best_lay@yahoo.com> wrote:

> On Wed, 19 Jun 2019 22:57:36 +0200, Carlos E.R. wrote:
>
>> I don't remember using "ed" in msdos, but surely it would have "edlin"
>> as well. Unless it was msdos 1 or 2, perhaps. I think 'ed' was for use
>> on batch files... I don't remember. I started with dos 3.20.
>
> I could be wrong but I don't think ed was ever released for
> DOS.
>
> Edlin was written by Patterson in 1980 and was part of 86-DOS
> (QDOS) that was purchased by MS.  It was included with every
> version of MSDOS from up to and including 5.  Legend has it
> that edlin was inspired by ed.

Edlin was just enough like CP/M's ed that you could use it
right away, and just enough unlike ed that it would bite you.

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  Fight low-contrast text in web pages!  http://contrastrebellion.com

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

#27295

FromAndreas Kohlbach <ank@spamfence.net>
Date2019-06-19 17:40 -0400
Message-ID<87o92tz22g.fsf@usenet.ankman.de>
In reply to#27292
On Wed, 19 Jun 2019 22:57:36 +0200, Carlos E.R. wrote:
>
> I don't remember using "ed" in msdos, but surely it would have "edlin"
> as well. Unless it was msdos 1 or 2, perhaps. I think 'ed' was for use
> on batch files... I don't remember. I started with dos 3.20.

Yes, might have been edlin. It's 30 years ago so I cannot remember the
name of the editor. Must have been an editor automatically installed on
an IBM PC from 1989 or before.
-- 
Andreas

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

#27297

FromGeorges <georges@prout.com>
Date2019-06-19 23:53 +0200
Message-ID<qeeat0$1e9o$1@gioia.aioe.org>
In reply to#27292
Le 19/06/2019 à 22:57, Carlos E.R. a écrit :
> On 19/06/2019 22.44, Andreas Kohlbach wrote:
>> On Wed, 19 Jun 2019 21:32:07 +0300, Tauno Voipio wrote:
>>>
>>> If you really want to go backward in time, you should use ed, and no
>>> newer derivatives like ex and vi with family.
>>
>> It was 1989 and I had to take a crash course for programmable logic
>> controller (using compressed air to move things around) when working at a
>> car manufacturer. Cannot remember why, but somebody suggested to write a
>> summary and have everybody of a group of about 20 get a copy. I suggested
>> to used the IBM PC sitting there idle for the two weeks the course would
>> take.
>>
>> I thought "Yeah, I know the Commodore Amiga and C64 and how to edit
>> documents. A PC cannot be much different". Of course I was wrong. The
>> only editor I found was ed (or ex?), running on MS-DOS who knows what
>> version. I never used such a primitive editor before and had no idea, how
>> to use it. There was no documentation and it took me a while only to
>> figure out how to go into insert-mode. The backspace key would (of
>> course, but little did I know) not work to correct a typo. So I killed
>> the program and restarted it some ten times to edit the document from
>> scratch until I made no typo. Finally a Mannesmann-Tally dot matrix
>> printer could put into action to produce 20 copies.
>>
>> Only recently, while running an Osborne I emulated, I learned how to use
>> these early text editors. Understanding they have different modes, like
>> "insert" or "command". Just like you would find it in vi today.
> 
> I don't remember using "ed" in msdos, but surely it would have "edlin"
> as well. Unless it was msdos 1 or 2, perhaps. I think 'ed' was for use
> on batch files... I don't remember. I started with dos 3.20.
> 
> 

edlin for sure, by the mid 80's we used 'vi' under Ultrix (non native
unix over vms) but it seems to me that there were clones already...

we wrote a subset of vi with turboC... ;D... (for student's pc-dos),
then we got 50 SunOs workstation... spending happy hours with yp, nfs,
bind and sendmail...

;)

-- 
()
/\

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

#27702

Fromruben safir <ruben@mrbrklyn.com>
Date2019-07-20 19:31 -0400
Message-ID<qh08ce$hul$1@reader2.panix.com>
In reply to#27258
On 6/19/19 4:20 AM, Carlos E.R. wrote:
> nope: on openSUSE we also have joe.
> 


and systemd and a fucked up lead commitee that is resentful and mean
spirited...

other than that, it is fine.

vi works and it is planted into the ecology of the text proccessing
world of unix.  If you don't want to use it, it is no sweat off my
backside.  Too me, VIM is massively over built and the cut and paste is
now badly broken and it will never be fixed.

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

#27201

From"Freenet" <pieer@free.fr>
Date2019-06-16 20:44 -0500
Message-ID<qe6r9m$7vi$1@neodome.net>
In reply to#27185
> 
> (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.

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

#27209

FromJasen Betts <jasen@xnet.co.nz>
Date2019-06-17 12:41 +0000
Message-ID<qe81p4$4t6$1@gonzo.revmaps.no-ip.org>
In reply to#27201
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>


-- 
  When I tried casting out nines I made a hash of it.

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

#27222

FromAndreas Kohlbach <ank@spamfence.net>
Date2019-06-17 17:30 -0400
Message-ID<87o92vkihl.fsf@usenet.ankman.de>
In reply to#27209
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.

F'up2 comp.os.linux.misc
-- 
Andreas

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

#27226

Fromowl <owl@rooftop.invalid>
Date2019-06-17 23:22 +0000
Message-ID<szbo9to3a.y4@rooftop.invalid>
In reply to#27222
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.

"               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
or hit F1, where brief instructions for quiting are just
a few lines in.

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

#27241

FromAndreas Kohlbach <ank@spamfence.net>
Date2019-06-18 16:07 -0400
Message-ID<87v9x2bqtr.fsf@usenet.ankman.de>
In reply to#27226
On Mon, 17 Jun 2019 23:22:26 +0000 (UTC), 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:
>>>
>>> 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.
>
> "               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
> or hit F1, where brief instructions for quiting are just
> a few lines in.

Yes. But "q!" could in my opinion be shown on that start screen
already so the newbie gets more essential information.
-- 
Andreas

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

#27259

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 10:28 +0200
Message-ID<0a8ptf-ogu.ln1@Telcontar.valinor>
In reply to#27226
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]

#27261

FromRich <rich@example.invalid>
Date2019-06-19 10:30 +0000
Message-ID<qed2rv$jos$1@dont-email.me>
In reply to#27259
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]

#27263

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 12:51 +0200
Message-ID<7mgptf-cg4.ln1@Telcontar.valinor>
In reply to#27261
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]

#27265

FromRich <rich@example.invalid>
Date2019-06-19 11:30 +0000
Message-ID<qed6ci$6d0$2@dont-email.me>
In reply to#27263
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]

#27276

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 21:03 +0200
Message-ID<khdqtf-7ho.ln1@Telcontar.valinor>
In reply to#27265
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]

#27267

Fromowl <owl@rooftop.invalid>
Date2019-06-19 12:30 +0000
Message-ID<ghiz003.agp5au@rooftop.invalid>
In reply to#27263
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]

#27270

FromCharlie Gibbs <cgibbs@kltpzyxm.invalid>
Date2019-06-19 18:23 +0000
Message-ID<qedujt013j9@news2.newsguy.com>
In reply to#27267
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.

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

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

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

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  Fight low-contrast text in web pages!  http://contrastrebellion.com

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

#27272

FromGeorges <georges@prout.com>
Date2019-06-19 20:42 +0200
Message-ID<qedvmp$1s09$1@gioia.aioe.org>
In reply to#27270
Le 19/06/2019 à 20:23, Charlie Gibbs a écrit :
> 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.
> 
>>> 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.
> 
>> 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.
> 
> 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...
> 

In fact, with 'vi', though I think it is possible with emacs, you do
need to look at your screen... If you know your file, or know what you
want to suppress or replace ;)

My favorite trick to prove 'vi' is quicker than a mouse editor :

Let's consider a file with 2 columns (or more of course), separated with
<space> or <tab> or whatever you want, you need to invert columns :

aaaaa bbbbb
aaaaa bbbbb

:1,$s/^\(.*\) \(.*\)$/\2 \1/

bbbbb aaaaa
bbbbb aaaaa

;)

-- 
()
/\

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

#27281

Fromowl <owl@rooftop.invalid>
Date2019-06-19 19:49 +0000
Message-ID<gyuz0z80vb3.g@rooftop.invalid>
In reply to#27272
Georges <georges@prout.com> wrote:
> Le 19/06/2019 à 20:23, Charlie Gibbs a écrit :
>> 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.
>> 
>>>> 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.
>> 
>>> 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.
>> 
>> 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...
>> 
> 
> In fact, with 'vi', though I think it is possible with emacs, you do
> need to look at your screen... If you know your file, or know what you
> want to suppress or replace ;)
> 
> My favorite trick to prove 'vi' is quicker than a mouse editor :
> 
> Let's consider a file with 2 columns (or more of course), separated with
> <space> or <tab> or whatever you want, you need to invert columns :
> 
> aaaaa bbbbb
> aaaaa bbbbb
> 
> :1,$s/^\(.*\) \(.*\)$/\2 \1/
> 
> bbbbb aaaaa
> bbbbb aaaaa
> 
> ;)
> 

You can replace the '1,$' with '%'.  ('%' means the whole file).
You can also use the \v switch to eliminate the need for escaping
the parentheses:

:%s/\v^(.*) (.*) (.*) (.*) (.*)$/\2 \1 \4 \5 \3/g

You could also let an external program do the work:

:%!awk '{print $2" "$1" "$4" "$5" "$3}'

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

#27283

FromGeorges <georges@prout.com>
Date2019-06-19 21:56 +0200
Message-ID<qee41l$ffe$1@gioia.aioe.org>
In reply to#27281
Le 19/06/2019 à 21:49, owl a écrit :
> Georges <georges@prout.com> wrote:

----8<----->8------
>> My favorite trick to prove 'vi' is quicker than a mouse editor :
>>
>> Let's consider a file with 2 columns (or more of course), separated with
>> <space> or <tab> or whatever you want, you need to invert columns :
>>
>> aaaaa bbbbb
>> aaaaa bbbbb
>>
>> :1,$s/^\(.*\) \(.*\)$/\2 \1/
>>
>> bbbbb aaaaa
>> bbbbb aaaaa
>>
>> ;)
>>
> 
> You can replace the '1,$' with '%'.  ('%' means the whole file).
> You can also use the \v switch to eliminate the need for escaping
> the parentheses:
> 
> :%s/\v^(.*) (.*) (.*) (.*) (.*)$/\2 \1 \4 \5 \3/g

This I didn't know, thank you ;)

this damn asymtotic learning curve,
40 years later you still learn tricks... ;D

nothing has the taste of 'vi' ;D

> 
> You could also let an external program do the work:
> 
> :%!awk '{print $2" "$1" "$4" "$5" "$3}'

sure...

-- 
()
/\

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

#27288

Fromowl <owl@rooftop.invalid>
Date2019-06-19 20:38 +0000
Message-ID<b8z9993ra.gahu34@rooftop.invalid>
In reply to#27283
Georges <georges@prout.com> wrote:
> Le 19/06/2019 à 21:49, owl a écrit :
>> Georges <georges@prout.com> wrote:
> 
> ----8<----->8------
>>> My favorite trick to prove 'vi' is quicker than a mouse editor :
>>>
>>> Let's consider a file with 2 columns (or more of course), separated with
>>> <space> or <tab> or whatever you want, you need to invert columns :
>>>
>>> aaaaa bbbbb
>>> aaaaa bbbbb
>>>
>>> :1,$s/^\(.*\) \(.*\)$/\2 \1/
>>>
>>> bbbbb aaaaa
>>> bbbbb aaaaa
>>>
>>> ;)
>>>
>> 
>> You can replace the '1,$' with '%'.  ('%' means the whole file).
>> You can also use the \v switch to eliminate the need for escaping
>> the parentheses:
>> 
>> :%s/\v^(.*) (.*) (.*) (.*) (.*)$/\2 \1 \4 \5 \3/g
> 
> This I didn't know, thank you ;)
> 
> this damn asymtotic learning curve,
> 40 years later you still learn tricks... ;D
> 
> nothing has the taste of 'vi' ;D
> 
>> 
>> You could also let an external program do the work:
>> 
>> :%!awk '{print $2" "$1" "$4" "$5" "$3}'
> 
> sure...
> 

If you have an android phone, you definitely need to get droidvim.
You don't even need to use the hacker's keyboard or map jk, since
it brings its own <esc> key. :)

https://play.google.com/store/apps/details?id=com.droidvim&hl=en_US

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

Page 6 of 14 — ← Prev page 1 … 4 5 [6] 7 8 … 14  Next page →

Back to top | Article view | comp.os.linux.misc

csiph-web