Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #27185 > unrolled thread
| Started by | "anonymous" <anonymous@rip.ax.lt> |
|---|---|
| First post | 2019-06-16 07:53 -0500 |
| Last post | 2019-06-25 15:11 +0200 |
| Articles | 20 on this page of 275 — 44 participants |
Back to article view | Back to comp.os.linux.misc
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 1 of 14 [1] 2 3 … 14 Next page →
| From | "anonymous" <anonymous@rip.ax.lt> |
|---|---|
| Date | 2019-06-16 07:53 -0500 |
| Subject | Linux Command-Line Editors Vulnerable to High-Severity Bug |
| Message-ID | <qe5e54$opq$1@neodome.net> |
(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.) A bug impacting editors Vim and Neovim could allow a trojan code to escape sandbox mitigations. https://threatpost.com/linux-command-line-editors-high-severity- bug/145569/
[toc] | [next] | [standalone]
| From | "Anonymous" <nobody@mixmin.net> |
|---|---|
| Date | 2019-06-16 07:56 -0500 |
| Message-ID | <qe5eaj$ovh$1@neodome.net> |
| In reply to | #27185 |
<https://threatpost.com/linux-command-line-editors-high-severity- bug/145569/>
[toc] | [prev] | [next] | [standalone]
| From | Fenris <fenris@invalid.invalid> |
|---|---|
| Date | 2019-06-16 15:53 +0200 |
| Message-ID | <Pine.NEB.4.64.1906161550430.29663@norge.freeshell.org> |
| In reply to | #27185 |
On Sun, 16 Jun 2019, anonymous 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.) Once you ware a admin for several unix flavours you may know why.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2019-06-16 15:35 +0100 |
| Message-ID | <qe5k3g$8on$2@dont-email.me> |
| In reply to | #27187 |
On 16/06/2019 14:53, Fenris wrote: > On Sun, 16 Jun 2019, anonymous 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.) > > Once you ware a admin for several unix flavours you may know why. vi was all one could rely on. I have written thousands of lines in vi. -- "Corbyn talks about equality, justice, opportunity, health care, peace, community, compassion, investment, security, housing...." "What kind of person is not interested in those things?" "Jeremy Corbyn?"
[toc] | [prev] | [next] | [standalone]
| From | Roger Blake <rogblake@iname.invalid> |
|---|---|
| Date | 2019-06-16 15:30 +0000 |
| Message-ID | <20190616112201@news.eternal-september.org> |
| In reply to | #27188 |
On 2019-06-16, The Natural Philosopher <tnp@invalid.invalid> wrote: > vi was all one could rely on. I have written thousands of lines in vi. Same here. Probably the thing to do is add "set nomodeline" to the system-wide vim configuration (/etc/vim/vimrc.local). On at least one system I spot-checked this was already in the system-wide vimrc with a comment that this is a dangerous feature. -- ----------------------------------------------------------------------------- Roger Blake (Posts from Google Groups killfiled due to excess spam.) NSA sedition and treason -- http://www.DeathToNSAthugs.com Don't talk to cops! -- http://www.DontTalkToCops.com Badges don't grant extra rights -- http://www.CopBlock.org -----------------------------------------------------------------------------
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2019-06-16 16:53 -0400 |
| Message-ID | <87r27tckv3.fsf@usenet.ankman.de> |
| In reply to | #27188 |
On Sun, 16 Jun 2019 15:35:28 +0100, The Natural Philosopher wrote: > > On 16/06/2019 14:53, Fenris wrote: >> On Sun, 16 Jun 2019, anonymous 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.) >> >> Once you ware a admin for several unix flavours you may know why. > > vi was all one could rely on. I have written thousands of lines in vi. Before I switched to Emacs Gnus I used slrn as newsreader, and the editor of choice was vi. F'up comp.os.linux.misc -- Andreas My random thoughts and comments https://news-commentaries.blogspot.com/
[toc] | [prev] | [next] | [standalone]
| From | "School of Agriculture" <ag@hick.edu> |
|---|---|
| Date | 2019-06-17 14:35 -0500 |
| Message-ID | <qe8q2c$9f8$1@news.mixmin.net> |
| In reply to | #27187 |
> > On Sun, 16 Jun 2019, anonymous 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.) > > Once you ware a admin for several unix flavours you may know why. Isn't nano available on all flavors of Linux?
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2019-06-17 20:42 +0100 |
| Message-ID | <qe8qfh$n19$1@dont-email.me> |
| In reply to | #27214 |
On 17/06/2019 20:35, School of Agriculture wrote: >> >> On Sun, 16 Jun 2019, anonymous 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.) >> >> Once you ware a admin for several unix flavours you may know why. > > Isn't nano available on all flavors of Linux? > Not in 1985 -- In a Time of Universal Deceit, Telling the Truth Is a Revolutionary Act. - George Orwell
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2019-06-17 17:31 -0400 |
| Message-ID | <87lfxzkieo.fsf@usenet.ankman.de> |
| In reply to | #27215 |
On Mon, 17 Jun 2019 20:42:41 +0100, The Natural Philosopher wrote: > > On 17/06/2019 20:35, School of Agriculture wrote: >>> >>> On Sun, 16 Jun 2019, anonymous 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.) >>> >>> Once you ware a admin for several unix flavours you may know why. >> >> Isn't nano available on all flavors of Linux? >> > Not in 1985 There was no Linux in 1985. But Live Aid. :-D -- Andreas My random thoughts and comments https://news-commentaries.blogspot.com/
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2019-06-18 14:13 +0100 |
| Message-ID | <qeao13$u92$4@dont-email.me> |
| In reply to | #27223 |
On 17/06/2019 22:31, Andreas Kohlbach wrote: > On Mon, 17 Jun 2019 20:42:41 +0100, The Natural Philosopher wrote: >> >> On 17/06/2019 20:35, School of Agriculture wrote: >>>> >>>> On Sun, 16 Jun 2019, anonymous 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.) >>>> >>>> Once you ware a admin for several unix flavours you may know why. >>> >>> Isn't nano available on all flavors of Linux? >>> >> Not in 1985 > > There was no Linux in 1985. Exactly. But there was Unix. But Live Aid. :-D Andt that cunt Geldof, pretending to save te world, but actually introducing warfare and ethic cleansing and boosting his bank account > -- "And if the blind lead the blind, both shall fall into the ditch". Gospel of St. Mathew 15:14
[toc] | [prev] | [next] | [standalone]
| From | Roger Blake <rogblake@iname.invalid> |
|---|---|
| Date | 2019-06-17 20:30 +0000 |
| Message-ID | <20190617162751@news.eternal-september.org> |
| In reply to | #27214 |
On 2019-06-17, School of Agriculture <ag@hick.edu> wrote: > Isn't nano available on all flavors of Linux? The best editor is the one you don't have to think about, where muscle memory takes over. I've been using vi since the early 1980s starting on BSD 4.1 and using it is transparent at this point. I have to stop and think to use nano. (I would not necessarily recommend vi/vim to someone just starting out though.) -- ----------------------------------------------------------------------------- Roger Blake (Posts from Google Groups killfiled due to excess spam.) NSA sedition and treason -- http://www.DeathToNSAthugs.com Don't talk to cops! -- http://www.DontTalkToCops.com Badges don't grant extra rights -- http://www.CopBlock.org -----------------------------------------------------------------------------
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-17 23:11 +0200 |
| Message-ID | <qe8vml$1o1m$2@gioia.aioe.org> |
| In reply to | #27218 |
Le 17/06/2019 à 22:30, Roger Blake a écrit : > On 2019-06-17, School of Agriculture <ag@hick.edu> wrote: >> Isn't nano available on all flavors of Linux? > > The best editor is the one you don't have to think about, where muscle > memory takes over. I've been using vi since the early 1980s starting on > BSD 4.1 and using it is transparent at this point. I have to stop and > think to use nano. (I would not necessarily recommend vi/vim to someone > just starting out though.) > One should learn "vi" (not vim) at least for those reasons : - the only text editor in maintenance mode (single user mode from boot) - very fast and light (even through remote connections) - include ex and ed, useful for solving complex searches/replacements Emacs is also a good candidate but, despite they have the same asymptotic learning curve (after years you will still discover new features), is : - very slow on remote connection - if you are used to xemacs, need for exporting display ;) -- () /\
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2019-06-17 17:36 -0400 |
| Message-ID | <87imt3ki78.fsf@usenet.ankman.de> |
| In reply to | #27221 |
On Mon, 17 Jun 2019 23:11:51 +0200, Georges wrote: > > Le 17/06/2019 à 22:30, Roger Blake a écrit : >> On 2019-06-17, School of Agriculture <ag@hick.edu> wrote: >>> Isn't nano available on all flavors of Linux? >> >> The best editor is the one you don't have to think about, where muscle >> memory takes over. I've been using vi since the early 1980s starting on >> BSD 4.1 and using it is transparent at this point. I have to stop and >> think to use nano. (I would not necessarily recommend vi/vim to someone >> just starting out though.) >> > > One should learn "vi" (not vim) at least for those reasons : > > - the only text editor in maintenance mode (single user mode from boot) > - very fast and light (even through remote connections) > - include ex and ed, useful for solving complex searches/replacements vi can run regex on files. Is that because it includes ex and/or ed? Never heard of that. > Emacs is also a good candidate but, despite they have the same > asymptotic learning curve (after years you will still discover new > features), is : > > - very slow on remote connection > - if you are used to xemacs, need for exporting display > > ;) As mentioned I run Gnus Emacs as newsreader here (see header of this post). I run it on a TTY, so no X involved. I start it on the command line with emacs -nw -f gnus F'up2 comp.os.linux.misc -- Andreas
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2019-06-17 18:27 -0400 |
| Message-ID | <qe945a$bdm$1@dont-email.me> |
| In reply to | #27221 |
Georges <georges@prout.com> writes: > Le 17/06/2019 à 22:30, Roger Blake a écrit : >> On 2019-06-17, School of Agriculture <ag@hick.edu> wrote: >>> Isn't nano available on all flavors of Linux? >> >> The best editor is the one you don't have to think about, where muscle >> memory takes over. I've been using vi since the early 1980s starting on >> BSD 4.1 and using it is transparent at this point. I have to stop and >> think to use nano. (I would not necessarily recommend vi/vim to someone >> just starting out though.) >> > > One should learn "vi" (not vim) at least for those reasons : > > - the only text editor in maintenance mode (single user mode from boot) > - very fast and light (even through remote connections) > - include ex and ed, useful for solving complex searches/replacements > > Emacs is also a good candidate but, despite they have the same > asymptotic learning curve (after years you will still discover new > features), is : > > - very slow on remote connection I used Emacs on remote connections for years. Every once in a while I'd run into something causing a slowdown. Like active roll over regions in a buffer. But, mostly not a problem. > - if you are used to xemacs, need for exporting display Sorry, can't parse this at all. Are you referencing XEmacs? That's pretty much a defunct project. Do you mean GNU Emacs in a X Window of it's own? Emacs can be slower in it's own window than in a terminal window, but as I said above, I found it mostly okay. As far as the security bug, Emacs allows for files to contain various things that filter into your environment, but it looks to me like the Emacs developers have been very careful to keep this interface safe. You can't just stick something in a file that Emacs will just go and execute. Most of my files end with something like this: # Local Variables: # compile-command: "./stack.py -name test stack.data" # End: So, if I visit a malware file, I might get my compile command changed, but I still need to invoke compile and then I'll see the command before I hit enter. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-18 08:45 +0200 |
| Message-ID | <qea1at$509$1@gioia.aioe.org> |
| In reply to | #27225 |
Le 18/06/2019 à 00:27, Dan Espen a écrit : > Georges <georges@prout.com> writes: > >> Le 17/06/2019 à 22:30, Roger Blake a écrit : >>> On 2019-06-17, School of Agriculture <ag@hick.edu> wrote: >>>> Isn't nano available on all flavors of Linux? >>> >>> The best editor is the one you don't have to think about, where muscle >>> memory takes over. I've been using vi since the early 1980s starting on >>> BSD 4.1 and using it is transparent at this point. I have to stop and >>> think to use nano. (I would not necessarily recommend vi/vim to someone >>> just starting out though.) >>> >> >> One should learn "vi" (not vim) at least for those reasons : >> >> - the only text editor in maintenance mode (single user mode from boot) >> - very fast and light (even through remote connections) >> - include ex and ed, useful for solving complex searches/replacements >> >> Emacs is also a good candidate but, despite they have the same >> asymptotic learning curve (after years you will still discover new >> features), is : >> >> - very slow on remote connection > > I used Emacs on remote connections for years. > Every once in a while I'd run into something causing a slowdown. > Like active roll over regions in a buffer. > > But, mostly not a problem. > >> - if you are used to xemacs, need for exporting display > > Sorry, can't parse this at all. > Are you referencing XEmacs? That's pretty much a defunct project. > Do you mean GNU Emacs in a X Window of it's own? yes, you are right... not clear... I was referencing emacsx - gnu emacs. anyway I won't fight to know which is better simply because I started with 'vi' in the very 80's ;) the only thing I like with emacs is the gnus newsreader (not here ;)) In maintenance mode context and embedded linux/unix 'vi' is still a good candidate ;) > Emacs can be slower in it's own window than in a terminal window, > but as I said above, I found it mostly okay. ok, i didn't know the -nw feature > > As far as the security bug, Emacs allows for files to contain > various things that filter into your environment, but it looks to > me like the Emacs developers have been very careful to keep this > interface safe. You can't just stick something in a file that > Emacs will just go and execute. > > Most of my files end with something like this: > > # Local Variables: > # compile-command: "./stack.py -name test stack.data" > # End: > > So, if I visit a malware file, I might get my compile command > changed, but I still need to invoke compile and then > I'll see the command before I hit enter. > interesting, thank you ;) -- () /\
[toc] | [prev] | [next] | [standalone]
| From | Charlie Gibbs <cgibbs@kltpzyxm.invalid> |
|---|---|
| Date | 2019-06-18 23:58 +0000 |
| Message-ID | <qebtrh098d@news2.newsguy.com> |
| In reply to | #27221 |
On 2019-06-17, Georges <georges@prout.com> wrote: > Le 17/06/2019 à 22:30, Roger Blake a écrit : > >> On 2019-06-17, School of Agriculture <ag@hick.edu> wrote: >> >>> Isn't nano available on all flavors of Linux? >> >> The best editor is the one you don't have to think about, where muscle >> memory takes over. I've been using vi since the early 1980s starting on >> BSD 4.1 and using it is transparent at this point. I have to stop and >> think to use nano. (I would not necessarily recommend vi/vim to someone >> just starting out though.) I've gotten vi far enough into my fingers that sometimes when in another editor, I'll see a string of "j"s appear on the screen, and realize I'm trying to move down a few lines. > One should learn "vi" (not vim) at least for those reasons : > > - the only text editor in maintenance mode (single user mode from boot) > - very fast and light (even through remote connections) > - include ex and ed, useful for solving complex searches/replacements The same argument (alas) applies to Notepad on Windows. > Emacs is also a good candidate but, despite they have the same > asymptotic learning curve (after years you will still discover new > features), is : > > - very slow on remote connection > - if you are used to xemacs, need for exporting display > > ;) I took a look at emacs a while ago, but there are some philosophical differences that I just can't wrap my head around. At least not without warping my world view more than I'm willing to do at this time. (Mostly to do with tabs...) -- /~\ 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]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2019-06-18 21:42 -0400 |
| Message-ID | <qec3tm$9vt$1@dont-email.me> |
| In reply to | #27249 |
Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes: > On 2019-06-17, Georges <georges@prout.com> wrote: > >> Le 17/06/2019 à 22:30, Roger Blake a écrit : >> >>> On 2019-06-17, School of Agriculture <ag@hick.edu> wrote: >>> >>>> Isn't nano available on all flavors of Linux? >>> >>> The best editor is the one you don't have to think about, where muscle >>> memory takes over. I've been using vi since the early 1980s starting on >>> BSD 4.1 and using it is transparent at this point. I have to stop and >>> think to use nano. (I would not necessarily recommend vi/vim to someone >>> just starting out though.) > > I've gotten vi far enough into my fingers that sometimes when in > another editor, I'll see a string of "j"s appear on the screen, > and realize I'm trying to move down a few lines. I look for one way to move the pointer. My window manager supports "j" to navigate menus, but it also supports the arrow keys. So many other things are hard wired into the cursor keys. I don't care so much that down arrow is right under my strongest finger, I just want one way to move down a line. >> One should learn "vi" (not vim) at least for those reasons : >> >> - the only text editor in maintenance mode (single user mode from boot) >> - very fast and light (even through remote connections) >> - include ex and ed, useful for solving complex searches/replacements > > The same argument (alas) applies to Notepad on Windows. I'll always remember users reporting they opened a UNIX file in Notepad and there was nothing there. I'd suggest, use Wordpad instead. Always. >> Emacs is also a good candidate but, despite they have the same >> asymptotic learning curve (after years you will still discover new >> features), is : >> >> - very slow on remote connection >> - if you are used to xemacs, need for exporting display >> >> ;) > > I took a look at emacs a while ago, but there are some philosophical > differences that I just can't wrap my head around. At least not > without warping my world view more than I'm willing to do at this > time. (Mostly to do with tabs...) Some time in the 70s I first saw Emacs and vi. At least with Emacs, I would hit some keys and text would appear. Doubtless you ran into Emacs trying to be helpful, TAB often means, indent this text according to Emacs' reading of syntax. The pointer won't move, just the text if it needs indenting. That can make a user think the TAB key isn't working, but it's checking syntax and only adjusting text if needed. Easy to turn off. I never would. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | Charlie Gibbs <cgibbs@kltpzyxm.invalid> |
|---|---|
| Date | 2019-06-19 18:23 +0000 |
| Message-ID | <qedujt113j9@news2.newsguy.com> |
| In reply to | #27251 |
On 2019-06-19, Dan Espen <dan1espen@gmail.com> wrote: > Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes: > >> On 2019-06-17, Georges <georges@prout.com> wrote: >> >>> One should learn "vi" (not vim) at least for those reasons : >>> >>> - the only text editor in maintenance mode (single user mode from boot) >>> - very fast and light (even through remote connections) >>> - include ex and ed, useful for solving complex searches/replacements >> >> The same argument (alas) applies to Notepad on Windows. > > I'll always remember users reporting they opened a UNIX file in Notepad > and there was nothing there. I'd suggest, use Wordpad instead. Always. When I open a file with naked LF line terminators in Notepad, it mashes the whole thing into one long line (which it then breaks up into whatever maximum length it can handle), with a little box glyph in place of the line breaks. Funny, LIST.COM (an old MS-DOS utility which I still use to examine files because it's so damned easy to use) accepts such files with no problems. >>> Emacs is also a good candidate but, despite they have the same >>> asymptotic learning curve (after years you will still discover new >>> features), is : >>> >>> - very slow on remote connection >>> - if you are used to xemacs, need for exporting display >>> >>> ;) >> >> I took a look at emacs a while ago, but there are some philosophical >> differences that I just can't wrap my head around. At least not >> without warping my world view more than I'm willing to do at this >> time. (Mostly to do with tabs...) > > Some time in the 70s I first saw Emacs and vi. > At least with Emacs, I would hit some keys and text would appear. > > Doubtless you ran into Emacs trying to be helpful, TAB often means, > indent this text according to Emacs' reading of syntax. The pointer > won't move, just the text if it needs indenting. That can make a > user think the TAB key isn't working, but it's checking syntax and > only adjusting text if needed. > > Easy to turn off. I never would. I think the philosophical difference I tripped over is that in Emacs, TAB isn't a character in the file, but a command to Emacs itself. I've stuck with the admittedly despicable practice of mixing tabs and spaces in my C programs so I can have 4-space indentation with a minimum of hassle. Some day, if I ever decide to eliminate tabs from source files, I'll take another look at Emacs. Meanwhile, the convention of one tab every 8 characters means any usage of tabs other than mine would restrict me to editors with sophisticated tab handling, like Emacs (and maybe vi), if I figure out whether and how to configure them. This could cause problems with things that are hardwired to 8-character tabs, e.g. cat and lpr. It's a thorny problem, and one I don't yet have time to address. -- /~\ 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]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-20 23:06 +0200 |
| Message-ID | <k39ttf-6mq.ln1@Telcontar.valinor> |
| In reply to | #27269 |
On 19/06/2019 20.23, Charlie Gibbs wrote: > On 2019-06-19, Dan Espen <dan1espen@gmail.com> wrote: > >> Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes: >> >>> On 2019-06-17, Georges <georges@prout.com> wrote: >>> >>>> One should learn "vi" (not vim) at least for those reasons : >>>> >>>> - the only text editor in maintenance mode (single user mode from boot) >>>> - very fast and light (even through remote connections) >>>> - include ex and ed, useful for solving complex searches/replacements >>> >>> The same argument (alas) applies to Notepad on Windows. >> >> I'll always remember users reporting they opened a UNIX file in Notepad >> and there was nothing there. I'd suggest, use Wordpad instead. Always. > > When I open a file with naked LF line terminators in Notepad, it > mashes the whole thing into one long line (which it then breaks up > into whatever maximum length it can handle), with a little box glyph > in place of the line breaks. Funny, LIST.COM (an old MS-DOS utility > which I still use to examine files because it's so damned easy to use) > accepts such files with no problems. > >>>> Emacs is also a good candidate but, despite they have the same >>>> asymptotic learning curve (after years you will still discover new >>>> features), is : >>>> >>>> - very slow on remote connection >>>> - if you are used to xemacs, need for exporting display >>>> >>>> ;) >>> >>> I took a look at emacs a while ago, but there are some philosophical >>> differences that I just can't wrap my head around. At least not >>> without warping my world view more than I'm willing to do at this >>> time. (Mostly to do with tabs...) >> >> Some time in the 70s I first saw Emacs and vi. >> At least with Emacs, I would hit some keys and text would appear. >> >> Doubtless you ran into Emacs trying to be helpful, TAB often means, >> indent this text according to Emacs' reading of syntax. The pointer >> won't move, just the text if it needs indenting. That can make a >> user think the TAB key isn't working, but it's checking syntax and >> only adjusting text if needed. >> >> Easy to turn off. I never would. > > I think the philosophical difference I tripped over is that in Emacs, > TAB isn't a character in the file, but a command to Emacs itself. > I've stuck with the admittedly despicable practice of mixing tabs > and spaces in my C programs so I can have 4-space indentation with > a minimum of hassle. Some day, if I ever decide to eliminate tabs > from source files, I'll take another look at Emacs. Meanwhile, the > convention of one tab every 8 characters means any usage of tabs > other than mine would restrict me to editors with sophisticated > tab handling, like Emacs (and maybe vi), if I figure out whether > and how to configure them. This could cause problems with things > that are hardwired to 8-character tabs, e.g. cat and lpr. > > It's a thorny problem, and one I don't yet have time to address. I used tabs of 3 chars ;-) When I was using floppies, I remember replacing chars with tabs on pascal programs to save on file size, on files that I didn't originate. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | rlhamil@bigapple.pri (Richard L. Hamilton) |
|---|---|
| Date | 2019-06-22 01:00 +0000 |
| Message-ID | <y4fPE.7$1v5.2@fx48.iad> |
| In reply to | #27249 |
In article <qebtrh098d@news2.newsguy.com>,
Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
> On 2019-06-17, Georges <georges@prout.com> wrote:
>
>> Le 17/06/2019 à 22:30, Roger Blake a écrit :
>>
>>> On 2019-06-17, School of Agriculture <ag@hick.edu> wrote:
>>>
>>>> Isn't nano available on all flavors of Linux?
>>>
>>> The best editor is the one you don't have to think about, where muscle
>>> memory takes over. I've been using vi since the early 1980s starting on
>>> BSD 4.1 and using it is transparent at this point. I have to stop and
>>> think to use nano. (I would not necessarily recommend vi/vim to someone
>>> just starting out though.)
>
> I've gotten vi far enough into my fingers that sometimes when in
> another editor, I'll see a string of "j"s appear on the screen,
> and realize I'm trying to move down a few lines.
>
>> One should learn "vi" (not vim) at least for those reasons :
>>
>> - the only text editor in maintenance mode (single user mode from boot)
>> - very fast and light (even through remote connections)
>> - include ex and ed, useful for solving complex searches/replacements
>
> The same argument (alas) applies to Notepad on Windows.
Notepad doesn't work over a ssh, telnet, or serial-terminal-like
connection. OTOH, not hard to install VIM for Windows (standalone,
don't need Cygwin or WSL); I've found it to work decently even SSH'd
into the Windows system (from a Mac, in my case).
--
ftp> get |fortune
377 I/O error: smart remark generator failed
Lasik/PRK theme music:
"In the Hall of the Mountain King", from "Peer Gynt"
(read act 2, scene 6 of the play if that doesn't make sense)
[toc] | [prev] | [next] | [standalone]
Page 1 of 14 [1] 2 3 … 14 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web