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 3 of 14 — ← Prev page 1 2 [3] 4 5 … 14 Next page →
| From | "J.O. Aho" <user@example.net> |
|---|---|
| Date | 2019-06-17 06:52 +0200 |
| Subject | Re: How come we're not talking about (Was: Linux Command-Line Editors Vulnerable to High-Severity Bug) |
| Message-ID | <gmokkrFl20kU1@mid.individual.net> |
| In reply to | #27193 |
On 16/06/2019 22.12, Kenny McCormack wrote: > In article <gmnjigFee8sU2@mid.individual.net>, > J.O. Aho <user@example.net> wrote: > ... >> Could just be the eternal flamewar between Emacs and Vi ;) > > How come all this idle chit-chat about editors and the people who use them, > and nothing about the supposed "vulnerability" (aka, security threat) > alluded to? > Maybe it's for the vulnerability is a few versions ago and people keep their machines up to date? There already been three updates since the flawed version and it's been blown up out of proportions. -- //Aho
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-16 22:47 +0200 |
| Message-ID | <qe69th$1pq2$2@gioia.aioe.org> |
| In reply to | #27192 |
Le 16/06/2019 ร 21:28, J.O. Aho a รฉcritย : > On 16/06/2019 18.57, Sir Gaygory's Owner's Owner ๐ถ็ฌ wrote: >> On Sun, 16 Jun 2019 07:53:55 -0500, LO AND BEHOLD; "anonymous" >> <anonymous@rip.ax.lt> determined that the following was of great >> importance and subsequently decided to freely share it with us in >> <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.) >> >> maybe because sometimes it's the only editor available on some systems. >> >> were you a sysadmin, you'd probably not have this jealous attitude. >> > > Could just be the eternal flamewar between Emacs and Vi ;) > > +1 :D
[toc] | [prev] | [next] | [standalone]
| From | Sir Gaygory's Owner's Owner ๐ถ็ฌ <root@127.0.0.1> |
|---|---|
| Date | 2019-06-21 13:24 -0500 |
| Message-ID | <PISdnQG50qhovZDAnZ2dnUU7-QHNnZ2d@giganews.com> |
| In reply to | #27192 |
On Sun, 16 Jun 2019 21:28:16 +0200, LO AND BEHOLD; "J.O. Aho" <user@example.net> determined that the following was of great importance and subsequently decided to freely share it with us in <gmnjigFee8sU2@mid.individual.net>: โกโกโกโกโกโกโกโกโกโกโก On 16/06/2019 18.57, ๐ฉ's Owner ๐ถ็ฌ wrote: โกโกโกโกโกโกโกโกโกโกโก โกโกโกโกโกโกโกโกโกโกโก On Sun, 16 Jun 2019 07:53:55 -0500, LO AND BEHOLD; "anonymous" โกโกโกโกโกโกโกโกโกโกโก โกโกโกโกโกโกโกโกโกโกโก <anonymous@rip.ax.lt> determined that the following was of great โกโกโกโกโกโกโกโกโกโกโก โกโกโกโกโกโกโกโกโกโกโก importance and subsequently decided to freely share it with us in โกโกโกโกโกโกโกโกโกโกโก โกโกโกโกโกโกโกโกโกโกโก <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.) maybe because sometimes it's the โกโกโกโกโกโกโกโกโกโกโก โกโกโกโกโกโกโกโกโกโกโก only editor available on some systems. were you a sysadmin, you'd โกโกโกโกโกโกโกโกโกโกโก โกโกโกโกโกโกโกโกโกโกโก probably not have this jealous attitude. โกโกโกโกโกโกโกโกโกโกโก โกโกโกโกโกโกโกโกโกโกโก Could just be the eternal flamewar between Emacs and Vi ;) i use both for different purposes, so i don't understand why anybody would want to be an evangelist for either. there's no reason to fire up emacs to comment out a line in a config file, IMO, and i wouldn't want to edit 2000+ lines of code without syntax-highlighting and mouse scrolling in vi. -- [THIS POAST HAS PASSED TRIMCHECKยฎ VALIDATION] THIS SPACE FOR RENT https://www.youtube.com/watch?v=iB6B8jGSdLA "Thanks to muzzies and their apologist-enablers like puppy whistle, this seems to be the new norm in the world. It's spreading like a cancer, and it's time we admit we're at war with pure evil. We need to put an end to this muzzie plague, or life on Earth is going to become pure hell everywhere. We need to get these people out of every civilized country, and there's only one way to do it. IOW, we have to become like them, with an emphasis on expediency over cruelty." - Checkmate (of alt.checkmate) "Pussy Willow has just proven that Trump's crackdown on previously unenforced immigration policies is working. We'll deal with the domestic terrorists as needed, but we don't need to be letting the muzzie terrorists get a foothold in our country too. One need only look at what they're doing in Europe right now to know we're doing the right thing by keeping them out, which is our right and our duty. - Checkmate (#1 pussy willow fan) - "You just made puppy whistle's sig line longer." - Janithor - "If I have a complaint about the (Southern Poverty) Law Center's description (of the alt-right movement), it is the phrase "heavy use of social media," which implies the alt-right is a real-world movement which uses a lot of social media. This is backwards: it is an online movement which occasionally appears in the real world. Where it gets punched." - Jason Rhode - "I think we should destroy every last fucking mosque in America." - "Checkmate, DoW #1" <Lunatic.Fringe@The.Edge> proves for us that white males are violent in Message-ID: <MPG.32c5bfefd18c9a698f0a8@news.altopia.com> - Golden Killfile, June 2005 KOTM, November 2006 Bob Allisat Memorial Hook, Line & Sinker, November 2006 Special Ops Cody Memorial Purple Heart, November 2006 Special Ops Cody Memorial Purple Heart, September 2007 Tony Sidaway Memorial "Drama Queen" Award, November 2006 Busted Urinal Award, April 2007 Order of the Holey Sockpuppet, September 2007 Barbara Woodhouse Memorial Dog Whistle, September 2006 Barbara Woodhouse Memorial Dog Whistle, April 2008 Tinfoil Sombrero, February 2007 AUK Mascot, September 2007 Putting the Awards Out of Order to Screw With the OCD Fuckheads, March 2016
[toc] | [prev] | [next] | [standalone]
| From | Grant Taylor <gtaylor@tnetconsulting.net> |
|---|---|
| Date | 2019-06-16 11:12 -0600 |
| Message-ID | <qe5ta3$ut$1@tncsrv09.home.tnetconsulting.net> |
| In reply to | #27185 |
On 6/16/19 6:53 AM, anonymous wrote: > (I have never understood why anyone would want to waste their time > learning how to use that Vim crap. Perhaps you could learn if you took the time to ask why someone would want to do that. Note: Asking why someone wants to do something does not mean that you have to agree with it or do so yourself. > Just a foolish venture into egotistical intellectual chauvinism.) I disagree. Ego has nothing to do with it. It's simply the best tool that I've found for the job at hand. If a different tool works better for you, then use what you want. I've found vim to be quite fast and allow me to do many things that are difficult if not impossible to do in other editors. Some of which aren't possible even in simpler vi, ex, or ed. -- Grant. . . . unix || die
[toc] | [prev] | [next] | [standalone]
| From | Siri Cruise <chine.bleu@yahoo.com> |
|---|---|
| Date | 2019-06-16 13:26 -0700 |
| Message-ID | <chine.bleu-F17F3D.13261816062019@reader.eternal-september.org> |
| In reply to | #27185 |
In article <qe5e54$opq$1@neodome.net>, "anonymous" <anonymous@rip.ax.lt> 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.) You don't always have X-Windows or Aqua available, such as telnet, ssh, sudo. vi does a gui within a terminal window or terminal device. -- :-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted. @ 'I desire mercy, not sacrifice.' /|\ The first law of discordiamism: The more energy This post / \ to make order is nore energy made into entropy. insults Islam. Mohammed
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2019-06-16 13:34 -0700 |
| Message-ID | <gmnnehFf7etU1@mid.individual.net> |
| In reply to | #27194 |
On 6/16/19 1:26 PM, Siri Cruise wrote: > In article <qe5e54$opq$1@neodome.net>, "anonymous" <anonymous@rip.ax.lt> 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.) > > You don't always have X-Windows or Aqua available, such as telnet, ssh, sudo. vi > does a gui within a terminal window or terminal device. > It is also a very powerful text editor for situations where you have massive log files and the like. I tend to use BBEdit (and even that the free version) but I do not have the higher end needs that vi serves MUCH better... but I realize it does. It is sorta like LibreOffice and Word... LibreOffice works great for many things but Word is for "bigger" tasks. Or maybe even moreso -- GIMP and Photoshop. GIMP is wonderful but it is simply not a replacement for Photoshop. In this case the open source solution, vi, is the solution for "bigger" text editing tasks. -- Personal attacks from those who troll show their own insecurity. They cannot use reason to show the message to be wrong so they try to feel somehow superior by attacking the messenger. They cling to their attacks and ignore the message time and time again.
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-16 22:58 +0200 |
| Message-ID | <qe6agm$1sm0$2@gioia.aioe.org> |
| In reply to | #27195 |
Le 16/06/2019 ร 22:34, Snit a รฉcritย : > On 6/16/19 1:26 PM, Siri Cruise wrote: >> In article <qe5e54$opq$1@neodome.net>, "anonymous" >> <anonymous@rip.ax.lt> 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.) >> >> You don't always have X-Windows or Aqua available, such as telnet, >> ssh, sudo. vi >> does a gui within a terminal window or terminal device. >> > > It is also a very powerful text editor for situations where you have > massive log files and the like. I tend to use BBEdit (and even that the > free version) but I do not have the higher end needs that vi serves MUCH > better... but I realize it does. > > It is sorta like LibreOffice and Word... LibreOffice works great for > many things but Word is for "bigger" tasks. Or maybe even moreso -- GIMP > and Photoshop. GIMP is wonderful but it is simply not a replacement for > Photoshop. > > In this case the open source solution, vi, is the solution for "bigger" > text editing tasks. > hummm... 'vi' is the only text editor in standalone mode... the only way to deal in standalone is to learn 'vi', at least basics ;) -- () /\
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-19 10:20 +0200 |
| Message-ID | <ar7ptf-9tt.ln1@Telcontar.valinor> |
| In reply to | #27199 |
On 16/06/2019 22.58, Georges wrote: > Le 16/06/2019 ร 22:34, Snit a รฉcritย : >> On 6/16/19 1:26 PM, Siri Cruise wrote: >>> In article <qe5e54$opq$1@neodome.net>, "anonymous" >>> <anonymous@rip.ax.lt> 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.) >>> >>> You don't always have X-Windows or Aqua available, such as telnet, >>> ssh, sudo. vi >>> does a gui within a terminal window or terminal device. >>> >> >> It is also a very powerful text editor for situations where you have >> massive log files and the like. I tend to use BBEdit (and even that >> the free version) but I do not have the higher end needs that vi >> serves MUCH better... but I realize it does. >> >> It is sorta like LibreOffice and Word... LibreOffice works great for >> many things but Word is for "bigger" tasks. Or maybe even moreso -- >> GIMP and Photoshop. GIMP is wonderful but it is simply not a >> replacement for Photoshop. >> >> In this case the open source solution, vi, is the solution for >> "bigger" text editing tasks. >> > > hummm... > > 'vi' is the only text editor in standalone mode... nope: on openSUSE we also have joe. > the only way to deal in standalone is to learn 'vi', at least basics ;) > -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-19 10:55 +0200 |
| Message-ID | <qect9g$uip$1@gioia.aioe.org> |
| In reply to | #27258 |
Le 19/06/2019 ร 10:20, Carlos E.R. a รฉcritย : > On 16/06/2019 22.58, Georges wrote: >> Le 16/06/2019 ร 22:34, Snit a รฉcritย : >>> On 6/16/19 1:26 PM, Siri Cruise wrote: >>>> In article <qe5e54$opq$1@neodome.net>, "anonymous" >>>> <anonymous@rip.ax.lt> 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.) >>>> >>>> You don't always have X-Windows or Aqua available, such as telnet, >>>> ssh, sudo. vi >>>> does a gui within a terminal window or terminal device. >>>> >>> >>> It is also a very powerful text editor for situations where you have >>> massive log files and the like. I tend to use BBEdit (and even that >>> the free version) but I do not have the higher end needs that vi >>> serves MUCH better... but I realize it does. >>> >>> It is sorta like LibreOffice and Word... LibreOffice works great for >>> many things but Word is for "bigger" tasks. Or maybe even moreso -- >>> GIMP and Photoshop. GIMP is wonderful but it is simply not a >>> replacement for Photoshop. >>> >>> In this case the open source solution, vi, is the solution for >>> "bigger" text editing tasks. >>> >> >> hummm... >> >> 'vi' is the only text editor in standalone mode... > > nope: on openSUSE we also have joe. > >> the only way to deal in standalone is to learn 'vi', at least basics ;) >> > > ;) 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 ;) -- () /\
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-19 12:37 +0200 |
| Message-ID | <nsfptf-po3.ln1@Telcontar.valinor> |
| In reply to | #27260 |
On 19/06/2019 10.55, Georges wrote: > Le 19/06/2019 ร 10:20, Carlos E.R. a รฉcritย : >> On 16/06/2019 22.58, Georges wrote: >>> Le 16/06/2019 ร 22:34, Snit a รฉcritย : >>>> On 6/16/19 1:26 PM, Siri Cruise wrote: >>>>> In article <qe5e54$opq$1@neodome.net>, "anonymous" >>>>> <anonymous@rip.ax.lt> 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.) >>>>> >>>>> You don't always have X-Windows or Aqua available, such as telnet, >>>>> ssh, sudo. vi >>>>> does a gui within a terminal window or terminal device. >>>>> >>>> >>>> It is also a very powerful text editor for situations where you have >>>> massive log files and the like. I tend to use BBEdit (and even that >>>> the free version) but I do not have the higher end needs that vi >>>> serves MUCH better... but I realize it does. >>>> >>>> It is sorta like LibreOffice and Word... LibreOffice works great for >>>> many things but Word is for "bigger" tasks. Or maybe even moreso -- >>>> GIMP and Photoshop. GIMP is wonderful but it is simply not a >>>> replacement for Photoshop. >>>> >>>> In this case the open source solution, vi, is the solution for >>>> "bigger" text editing tasks. >>>> >>> >>> hummm... >>> >>> 'vi' is the only text editor in standalone mode... >> >> nope: on openSUSE we also have joe. >> >>> the only way to deal in standalone is to learn 'vi', at least basics ;) >>> >> >> > > ;) > > 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 ;) I wouldn't. I would show it, teach how to exit, how to enter edit mode to change a word or two, how to save or abort, then how to use anything they like instead. Learn vi on their own time if they wish. I do not consider it simple for a newcomer, who probably knows Windows already these days. The people I know would exit the class if I try to teach vi, calling me old man or worse. I know people that refuse to use Linux the instant they have to type a command on a terminal. They install Linux to try, then abort and try perhaps next year, hoping that they can click their entire way along. Tell one of those that they have to use "vi", waste an hour or two in class teaching it? No way. Same as I thought two decades ago when I first met it on January 1998. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-19 13:13 +0200 |
| Message-ID | <qed5d7$44l$1@gioia.aioe.org> |
| In reply to | #27262 |
Le 19/06/2019 ร 12:37, Carlos E.R. a รฉcritย : > On 19/06/2019 10.55, Georges wrote: >> Le 19/06/2019 ร 10:20, Carlos E.R. a รฉcritย : >>> On 16/06/2019 22.58, Georges wrote: >>>> Le 16/06/2019 ร 22:34, Snit a รฉcritย : >>>>> On 6/16/19 1:26 PM, Siri Cruise wrote: >>>>>> In article <qe5e54$opq$1@neodome.net>, "anonymous" >>>>>> <anonymous@rip.ax.lt> 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.) >>>>>> >>>>>> You don't always have X-Windows or Aqua available, such as telnet, >>>>>> ssh, sudo. vi >>>>>> does a gui within a terminal window or terminal device. >>>>>> >>>>> >>>>> It is also a very powerful text editor for situations where you have >>>>> massive log files and the like. I tend to use BBEdit (and even that >>>>> the free version) but I do not have the higher end needs that vi >>>>> serves MUCH better... but I realize it does. >>>>> >>>>> It is sorta like LibreOffice and Word... LibreOffice works great for >>>>> many things but Word is for "bigger" tasks. Or maybe even moreso -- >>>>> GIMP and Photoshop. GIMP is wonderful but it is simply not a >>>>> replacement for Photoshop. >>>>> >>>>> In this case the open source solution, vi, is the solution for >>>>> "bigger" text editing tasks. >>>>> >>>> >>>> hummm... >>>> >>>> 'vi' is the only text editor in standalone mode... >>> >>> nope: on openSUSE we also have joe. >>> >>>> the only way to deal in standalone is to learn 'vi', at least basics ;) >>>> >>> >>> >> >> ;) >> >> 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 ;) > > I wouldn't. I would show it, teach how to exit, how to enter edit mode > to change a word or two, how to save or abort, then how to use anything > they like instead. Learn vi on their own time if they wish. ;) exactly what I meant... (not 20h course on 'vi'... on unix tools...) thank you for excusing my poor english. > I do not > consider it simple for a newcomer, who probably knows Windows already > these days. The people I know would exit the class if I try to teach vi, > calling me old man or worse. ;D yes I do agree... > > I know people that refuse to use Linux the instant they have to type a > command on a terminal. They install Linux to try, then abort and try > perhaps next year, hoping that they can click their entire way along. I do agree too... sadly... But some people prefer linux, they generally are more than 60. They like its simpleness : - I install and configure an xfce/ubuntu, few big icons in the bottom (files, surf, photos and mail)... - I explain what to do when they see "updates"... and everything works as they want when they plug smartphones or cameras, using https://framatalk.org to 'video-chat' with their gran-children ;) Windows is not suited for beginners... ;) > > Tell one of those that they have to use "vi", waste an hour or two in > class teaching it? No way. ;D I agree... I tried with my son... 21yo... > Same as I thought two decades ago when I > first met it on January 1998. > no choice in the very 80's ;) -- () /\
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-20 14:31 +0200 |
| Message-ID | <ptastf-u13.ln1@Telcontar.valinor> |
| In reply to | #27264 |
On 19/06/2019 13.13, Georges wrote: > Le 19/06/2019 ร 12:37, Carlos E.R. a รฉcritย : >> On 19/06/2019 10.55, Georges wrote: >>> Le 19/06/2019 ร 10:20, Carlos E.R. a รฉcritย : >>>> On 16/06/2019 22.58, Georges wrote: >>>>> Le 16/06/2019 ร 22:34, Snit a รฉcritย : >>>>>> On 6/16/19 1:26 PM, Siri Cruise wrote: >>>>>>> In article <qe5e54$opq$1@neodome.net>, "anonymous" >>>>>>> <anonymous@rip.ax.lt> 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.) >>>>>>> >>>>>>> You don't always have X-Windows or Aqua available, such as telnet, >>>>>>> ssh, sudo. vi >>>>>>> does a gui within a terminal window or terminal device. >>>>>>> >>>>>> >>>>>> It is also a very powerful text editor for situations where you have >>>>>> massive log files and the like. I tend to use BBEdit (and even that >>>>>> the free version) but I do not have the higher end needs that vi >>>>>> serves MUCH better... but I realize it does. >>>>>> >>>>>> It is sorta like LibreOffice and Word... LibreOffice works great for >>>>>> many things but Word is for "bigger" tasks. Or maybe even moreso -- >>>>>> GIMP and Photoshop. GIMP is wonderful but it is simply not a >>>>>> replacement for Photoshop. >>>>>> >>>>>> In this case the open source solution, vi, is the solution for >>>>>> "bigger" text editing tasks. >>>>>> >>>>> >>>>> hummm... >>>>> >>>>> 'vi' is the only text editor in standalone mode... >>>> >>>> nope: on openSUSE we also have joe. >>>> >>>>> the only way to deal in standalone is to learn 'vi', at least basics ;) >>>>> >>>> >>>> >>> >>> ;) >>> >>> 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 ;) >> >> I wouldn't. I would show it, teach how to exit, how to enter edit mode >> to change a word or two, how to save or abort, then how to use anything >> they like instead. Learn vi on their own time if they wish. > > ;) exactly what I meant... (not 20h course on 'vi'... on unix tools...) > thank you for excusing my poor english. Ah, I misunderstood :-) > >> I do not >> consider it simple for a newcomer, who probably knows Windows already >> these days. The people I know would exit the class if I try to teach vi, >> calling me old man or worse. > > ;D yes I do agree... > >> >> I know people that refuse to use Linux the instant they have to type a >> command on a terminal. They install Linux to try, then abort and try >> perhaps next year, hoping that they can click their entire way along. > > I do agree too... sadly... Yes, but these people will never be happy on Linux. > But some people prefer linux, they generally are more than 60. > They like its simpleness : > - I install and configure an xfce/ubuntu, few big icons in the bottom > (files, surf, photos and mail)... > - I explain what to do when they see "updates"... > > and everything works as they want when they plug smartphones or cameras, > using https://framatalk.org to 'video-chat' with their gran-children ;) Indeed :-) > > Windows is not suited for beginners... ;) True, but they don't see it. It is "easy" because they are already familiar with it from school. > >> >> Tell one of those that they have to use "vi", waste an hour or two in >> class teaching it? No way. > > ;D I agree... I tried with my son... 21yo... :-D >> Same as I thought two decades ago when I >> first met it on January 1998. >> > > no choice in the very 80's ;) Right. But my first own computer (my previous contact with computers were borrowed machines, or in class, so limited time) was an IBM PC clone around 1984, running MsDos / Digital Dos Plus. I did not see any Unix till 1997. So the editors that were most familiar to me were WordStar family (Borland IDE), or WordPerfect. The first time I had to use a Linux machine (remotely, via telnet, 1998) I was terrified at the choice of editors. vi? emacs? wtf...? I edited files instead on Windows then transferred them to Linux. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | ruben safir <ruben@mrbrklyn.com> |
|---|---|
| Date | 2019-07-20 19:43 -0400 |
| Message-ID | <qh091l$fje$1@reader2.panix.com> |
| In reply to | #27319 |
On 6/20/19 8:31 AM, Carlos E.R. wrote: > I edited files instead on Windows > then transferred them to Linux. which was stupid.
[toc] | [prev] | [next] | [standalone]
| From | Grant Taylor <gtaylor@tnetconsulting.net> |
|---|---|
| Date | 2019-06-19 09:36 -0600 |
| Message-ID | <qedkr0$afk$1@tncsrv09.home.tnetconsulting.net> |
| In reply to | #27262 |
On 6/19/19 4:37 AM, Carlos E.R. wrote: > I wouldn't. I would show it, teach how to exit, how to enter edit > mode to change a word or two, how to save or abort, then how to use > anything they like instead. Learn vi on their own time if they wish. I feel like a five minute show and tell beyond the basics of "here are some things that you can do inside of $EDITOR if you want to go beyond what will be taught here" type thing is probably a good thing. Those that are interested will run with it. Those that aren't will not be unduly bothered. I think that vi (and probably Emacs) deserve 15 ~ 30 minutes (each). They are both prolific enough that it's good to have an exposure to them. That will likely give people enough information that they could use either of them if they must. (Think knowing how to drive a manual transmission and able to get to the hospital in an emergency.) Then they can make their own informed decision. -- Grant. . . . unix || die
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-20 14:36 +0200 |
| Message-ID | <88bstf-ka3.ln1@Telcontar.valinor> |
| In reply to | #27268 |
On 19/06/2019 17.36, Grant Taylor wrote: > On 6/19/19 4:37 AM, Carlos E.R. wrote: >> I wouldn't. I would show it, teach how to exit, how to enter edit mode >> to change a word or two, how to save or abort, then how to use >> anything they like instead. Learn vi on their own time if they wish. > > I feel like a five minute show and tell beyond the basics of "here are > some things that you can do inside of $EDITOR if you want to go beyond > what will be taught here" type thing is probably a good thing.ย Those > that are interested will run with it.ย Those that aren't will not be > unduly bothered. > > I think that vi (and probably Emacs) deserve 15 ~ 30 minutes (each). > > They are both prolific enough that it's good to have an exposure to them. > > That will likely give people enough information that they could use > either of them if they must.ย (Think knowing how to drive a manual > transmission and able to get to the hospital in an emergency.)ย Then > they can make their own informed decision. LOL. All my cars have been manual. I have never touched an automatic transmission vehicle, nor anyone I know! X-D But yes, I see your meaning and agree. Me, I have used emacs more than once, because it supports certain features that others don't and I have needed on occasion. With some difficulty and reluctance, but I managed fine :-) -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | ruben safir <ruben@mrbrklyn.com> |
|---|---|
| Date | 2019-07-20 19:37 -0400 |
| Message-ID | <qh08n7$t4t$1@reader2.panix.com> |
| In reply to | #27262 |
On 6/19/19 6:37 AM, Carlos E.R. 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 ;) > I wouldn't. I would show it, teach how to exit, how to enter edit mode > to change a word or two, how to save or abort, then how to use anything > they like instead. Learn vi on their own time if they wish. I do not > consider it simple for a newcomer, who probably knows Windows already > these days. The people I know would exit the class if I try to teach vi, > calling me old man or worse. I've taught these classes and what you propose is a bad idea. When you teach them Vi you very much teach them the Unix philosophy and unteaching windows BS is have the problem in teaching them Unix or Linux. Vi is simple for the newcomer to learn but they need to spend a couple of days learning it. And then they are learning ed, sed, and grep, and they stop thinking of there text editor as being a stupid devise like notepad. Job Number 1 for a newcomer is to get off the Microsoft crackpipe. It doesn't hurt them to learn basic EMACS as well.
[toc] | [prev] | [next] | [standalone]
| From | Tauno Voipio <tauno.voipio@notused.fi.invalid> |
|---|---|
| Date | 2019-06-19 21:32 +0300 |
| Message-ID | <qedv37$r1n$1@dont-email.me> |
| In reply to | #27260 |
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: >>> Le 16/06/2019 ร 22:34, Snit a รฉcritย : >>>> On 6/16/19 1:26 PM, Siri Cruise wrote: >>>>> In article <qe5e54$opq$1@neodome.net>, "anonymous" >>>>> <anonymous@rip.ax.lt> 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.) >>>>> >>>>> You don't always have X-Windows or Aqua available, such as telnet, >>>>> ssh, sudo. vi >>>>> does a gui within a terminal window or terminal device. >>>>> >>>> >>>> It is also a very powerful text editor for situations where you have >>>> massive log files and the like. I tend to use BBEdit (and even that >>>> the free version) but I do not have the higher end needs that vi >>>> serves MUCH better... but I realize it does. >>>> >>>> It is sorta like LibreOffice and Word... LibreOffice works great for >>>> many things but Word is for "bigger" tasks. Or maybe even moreso -- >>>> GIMP and Photoshop. GIMP is wonderful but it is simply not a >>>> replacement for Photoshop. >>>> >>>> In this case the open source solution, vi, is the solution for >>>> "bigger" text editing tasks. >>>> >>> >>> hummm... >>> >>> 'vi' is the only text editor in standalone mode... >> >> nope: on openSUSE we also have joe. >> >>> the only way to deal in standalone is to learn 'vi', at least basics ;) >>> >> >> > > ;) > > 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. -- -TV
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-19 20:47 +0200 |
| Message-ID | <qedvvf$1s09$2@gioia.aioe.org> |
| In reply to | #27271 |
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ย : >>> On 16/06/2019 22.58, Georges wrote: >>>> Le 16/06/2019 ร 22:34, Snit a รฉcritย : >>>>> On 6/16/19 1:26 PM, Siri Cruise wrote: >>>>>> In article <qe5e54$opq$1@neodome.net>, "anonymous" >>>>>> <anonymous@rip.ax.lt> 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.) >>>>>> >>>>>> You don't always have X-Windows or Aqua available, such as telnet, >>>>>> ssh, sudo. vi >>>>>> does a gui within a terminal window or terminal device. >>>>>> >>>>> >>>>> It is also a very powerful text editor for situations where you have >>>>> massive log files and the like. I tend to use BBEdit (and even that >>>>> the free version) but I do not have the higher end needs that vi >>>>> serves MUCH better... but I realize it does. >>>>> >>>>> It is sorta like LibreOffice and Word... LibreOffice works great for >>>>> many things but Word is for "bigger" tasks. Or maybe even moreso -- >>>>> GIMP and Photoshop. GIMP is wonderful but it is simply not a >>>>> replacement for Photoshop. >>>>> >>>>> In this case the open source solution, vi, is the solution for >>>>> "bigger" text editing tasks. >>>>> >>>> >>>> hummm... >>>> >>>> 'vi' is the only text editor in standalone mode... >>> >>> nope: on openSUSE we also have joe. >>> >>>> the only way to deal in standalone is to learn 'vi', at least basics ;) >>>> >>> >>> >> >> ;) >> >> 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 ;) -- () /\
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-19 21:01 +0200 |
| Message-ID | <4edqtf-7ho.ln1@Telcontar.valinor> |
| In reply to | #27273 |
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. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2019-06-19 20:23 +0100 |
| Message-ID | <qee233$ddk$3@dont-email.me> |
| In reply to | #27275 |
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 TBH when messing around with seriously complex tect manipluations I have been known to use grep , vi, and geany all on the same file. Geany slows down on hundred megabyte files. Vi doesnt seem to -- Any fool can believe in principles - and most of them do!
[toc] | [prev] | [next] | [standalone]
Page 3 of 14 — ← Prev page 1 2 [3] 4 5 … 14 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web