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 5 of 13 — ← Prev page 1 … 3 4 [5] 6 7 … 13  Next page →

#57060

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-21 13:03 +0200
Message-ID<f5qutf-bcq.ln1@Telcontar.valinor>
In reply to#57057
On 21/06/2019 09.17, The Natural Philosopher wrote:
> On 19/06/2019 21:53, Carlos E.R. wrote:
>> On 19/06/2019 21.23, The Natural Philosopher wrote:
>>> On 19/06/2019 20:01, Carlos E.R. wrote:
>>>> On 19/06/2019 20.47, Georges wrote:
>>>>> Le 19/06/2019 à 20:32, Tauno Voipio a écrit :
>>>>>> On 19.6.19 11:55, Georges wrote:
>>>>>>> Le 19/06/2019 à 10:20, Carlos E.R. a écrit :
>>>>
>>>> ...
>>>>
>>>>>>> if you teach students, you struggle between time and contents (what
>>>>>>> you
>>>>>>> can teach on a 20h course for instance), so 'vi' is a good choice
>>>>>>> because it's widely used... and simple... once you get the
>>>>>>> philosophy ;)
>>>>>>>
>>>>>>
>>>>>> If you really want to go backward in time, you should use ed, and no
>>>>>> newer derivatives like ex and vi with family.
>>>>>>
>>>>>> My favourite in primitive editors is nano.
>>>>>>
>>>>>
>>>>> Try this with nano... ;)
>>>>>
>>>>> 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
>>>>>
>>>>> ;)
>>>>>
>>>>
>>>> Jstar (joe) can do that.  Switch to vertical block mode, select the
>>>> rectangle on the left, move to the right.
>>>>
>>> in a Wysiwyg I just highlight the text and move it
>>
>> I don't know any such editor that can do that in Linux. Of course, I
>> have not tried all in existence.
>>
>> I can not just highlight all the 'b's. As I try, the 'a's in the
>> previous line gets highlighted. No vertical block mode.
> 
> I did it in geany easily
> 
> Obviously it has to be done one line at a time

Ah, that doesn't count. It has to move the entire column or rectangle at
a single operation.

-- 
Cheers, Carlos.

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

#56998

Fromowl <owl@rooftop.invalid>
Date2019-06-19 19:51 +0000
Message-ID<sv899zb3.gan33@rooftop.invalid>
In reply to#56993
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
> On 19/06/2019 20.47, Georges wrote:
>> Le 19/06/2019 à 20:32, Tauno Voipio a écrit :
>>> On 19.6.19 11:55, Georges wrote:
>>>> Le 19/06/2019 à 10:20, Carlos E.R. a écrit :
> 
> ...
> 
>>>> if you teach students, you struggle between time and contents (what you
>>>> can teach on a 20h course for instance), so 'vi' is a good choice
>>>> because it's widely used... and simple... once you get the philosophy ;)
>>>>
>>>
>>> If you really want to go backward in time, you should use ed, and no
>>> newer derivatives like ex and vi with family.
>>>
>>> My favourite in primitive editors is nano.
>>>
>> 
>> Try this with nano... ;)
>> 
>> 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
>> 
>> ;)
>> 
> 
> Jstar (joe) can do that.  Switch to vertical block mode, select the
> rectangle on the left, move to the right.
> 

Shuffling many columns would seem to be a pain that way.

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

#57005

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 22:45 +0200
Message-ID<4hjqtf-70u.ln1@Telcontar.valinor>
In reply to#56998
On 19/06/2019 21.51, owl wrote:
> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 19/06/2019 20.47, Georges wrote:
>>> Le 19/06/2019 à 20:32, Tauno Voipio a écrit :
>>>> On 19.6.19 11:55, Georges wrote:
>>>>> Le 19/06/2019 à 10:20, Carlos E.R. a écrit :
>>
>> ...
>>
>>>>> if you teach students, you struggle between time and contents (what you
>>>>> can teach on a 20h course for instance), so 'vi' is a good choice
>>>>> because it's widely used... and simple... once you get the philosophy ;)
>>>>>
>>>>
>>>> If you really want to go backward in time, you should use ed, and no
>>>> newer derivatives like ex and vi with family.
>>>>
>>>> My favourite in primitive editors is nano.
>>>>
>>>
>>> Try this with nano... ;)
>>>
>>> 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
>>>
>>> ;)
>>>
>>
>> Jstar (joe) can do that.  Switch to vertical block mode, select the
>> rectangle on the left, move to the right.
>>
> 
> Shuffling many columns would seem to be a pain that way.

Sure. But the times I had to do such a thing might be counted with my
fingers :-)



-- 
Cheers, Carlos.

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

#57787

Fromruben safir <ruben@mrbrklyn.com>
Date2019-07-20 19:46 -0400
Message-ID<qh097q$fje$2@reader2.panix.com>
In reply to#56993
On 6/19/19 3:01 PM, Carlos E.R. wrote:
> Jstar (joe) can do that.  Switch to vertical block mode, select the
> rectangle on the left, move to the right.

yeah that is fucked up.  You need to take you hands off the key board.

If I wanted a word processor, I would use open office.

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

#56992

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 21:00 +0200
Message-ID<nadqtf-7ho.ln1@Telcontar.valinor>
In reply to#56990
On 19/06/2019 20.32, Tauno Voipio wrote:
> On 19.6.19 11:55, Georges wrote:
>> Le 19/06/2019 à 10:20, Carlos E.R. a écrit :
>>> On 16/06/2019 22.58, Georges wrote:

...

>> if you teach students, you struggle between time and contents (what you
>> can teach on a 20h course for instance), so 'vi' is a good choice
>> because it's widely used... and simple... once you get the philosophy ;)
>>
> 
> If you really want to go backward in time, you should use ed, and no
> newer derivatives like ex and vi with family.

Edlin in msdos :-P

I once used a printer to edit autoexec.bat or config.sys, with a
non-working display. Edlin can do that. That got an rs232 connection
going to another computer that would act as emergency display.

> 
> My favourite in primitive editors is nano.
> 


-- 
Cheers, Carlos.

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

#56996

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2019-06-19 20:20 +0100
Message-ID<qee1u8$ddk$2@dont-email.me>
In reply to#56992
On 19/06/2019 20:00, Carlos E.R. wrote:

> 
> I once used a printer to edit autoexec.bat or config.sys, with a
> non-working display. Edlin can do that. That got an rs232 connection
> going to another computer that would act as emergency display.
> 

Try writing code on a flexowriter.




-- 
If I had all the money I've spent on drink...
..I'd spend it on drink.

Sir Henry (at Rawlinson's End)

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

#57030

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-20 14:43 +0200
Message-ID<7kbstf-ka3.ln1@Telcontar.valinor>
In reply to#56996
On 19/06/2019 21.20, The Natural Philosopher wrote:
> On 19/06/2019 20:00, Carlos E.R. wrote:
> 
>>
>> I once used a printer to edit autoexec.bat or config.sys, with a
>> non-working display. Edlin can do that. That got an rs232 connection
>> going to another computer that would act as emergency display.
>>
> 
> Try writing code on a flexowriter.

<https://en.wikipedia.org/wiki/Friden_Flexowriter>

Never used one, before my time. A lab on university was still using
cards (already obsolete by 1982), but they modernized before I had to
use them.

-- 
Cheers, Carlos.

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

#57004

FromAndreas Kohlbach <ank@spamfence.net>
Date2019-06-19 16:44 -0400
Message-ID<87blyt1f0t.fsf@usenet.ankman.de>
In reply to#56990
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.
-- 
Andreas

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

#57007

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-19 22:57 +0200
Message-ID<07kqtf-hou.ln1@Telcontar.valinor>
In reply to#57004
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.


-- 
Cheers, Carlos.

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

#57009

FromWildman <best_lay@yahoo.com>
Date2019-06-19 16:17 -0500
Message-ID<44ydnUGwJqwcO5fAnZ2dnUU7-IudnZ2d@giganews.com>
In reply to#57007
On Wed, 19 Jun 2019 22:57:36 +0200, Carlos E.R. wrote:

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

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.

-- 
<Wildman> GNU/Linux user #557453
The cow died so I don't need your bull!

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

#57011

FromAndreas Kohlbach <ank@spamfence.net>
Date2019-06-19 17:43 -0400
Message-ID<87lfxxz1wi.fsf@usenet.ankman.de>
In reply to#57009
On Wed, 19 Jun 2019 16:17:53 -0500, Wildman 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.

Suppose I though of ed for CP/M and on MS-DOS it was in fact edlin I used.
-- 
Andreas

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

#57013

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-20 00:58 +0200
Message-ID<69rqtf-3j4.ln1@Telcontar.valinor>
In reply to#57011
On 19/06/2019 23.43, Andreas Kohlbach wrote:
> On Wed, 19 Jun 2019 16:17:53 -0500, Wildman 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.
> 
> Suppose I though of ed for CP/M and on MS-DOS it was in fact edlin I used.

I think there was an ed, that did the role of "sed" in Linux, but less
powerful. Edlin was usable as editor, but it was a "line editor", not
suitable for a letter. I don't think it would do "wrap", but I don't
remember. Its role were config or batch files.

I stopped firefox for today, I need the ram for a virtual machine, or
I'd check the wikipedia. Maybe it says.


-- 
Cheers, Carlos.

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

#57010

FromAndreas Kohlbach <ank@spamfence.net>
Date2019-06-19 17:40 -0400
Message-ID<87o92tz22g.fsf@usenet.ankman.de>
In reply to#57007
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]

#57012

FromGeorges <georges@prout.com>
Date2019-06-19 23:53 +0200
Message-ID<qeeat0$1e9o$1@gioia.aioe.org>
In reply to#57007
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]

#57784

Fromruben safir <ruben@mrbrklyn.com>
Date2019-07-20 19:31 -0400
Message-ID<qh08ce$hul$1@reader2.panix.com>
In reply to#56978
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]

#56934

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

#56936

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#56934
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]

#56953

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

#56955

From"Carlos E.R." <robin_listas@es.invalid>
Date2019-06-18 11:29 +0200
Message-ID<7hnmtf-0bd.ln1@Telcontar.valinor>
In reply to#56953
On 18/06/2019 03.22, Carlos E.R. wrote:
> On 17/06/2019 23.30, Andreas Kohlbach 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.
> 
> And kill the opportunity of telling a good story about the time you had
> to hit the power switch because of not knowing how to exit vi, and hear
> the me toos from the back row?  :-D
> 
> 

Now, how did it happen that I wrote "alt.os.linux.suse" group above? It
was supposed to be "alt.os.linux".

Ah, I see why now while doing it again. Thunderbird tries to be too
clever :-(

-- 
Cheers, Carlos.

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

#56969

FromAndreas Kohlbach <ank@spamfence.net>
Date2019-06-18 16:15 -0400
Message-ID<87sgs6bqgr.fsf@usenet.ankman.de>
In reply to#56955
On Tue, 18 Jun 2019 11:29:43 +0200, Carlos E.R. wrote:
>
> Now, how did it happen that I wrote "alt.os.linux.suse" group above? It
> was supposed to be "alt.os.linux".
>
> Ah, I see why now while doing it again. Thunderbird tries to be too
> clever :-(

Because I set a Followup-To: to avoid cross posting.

Okay, you put the other groups back. Since SUSE is mentioned one could
add the Debian, RedHat, Fedora... groups.

Furthermore this might be off topic in any group dealing with Linux since
the topic is about and editor running on UNIX and other operating systems
too and there should be a group having editors as topic. At least the
de.* hierarchy has.
-- 
Andreas

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

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

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

csiph-web