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 8 of 14 — ← Prev page 1 … 6 7 [8] 9 10 … 14 Next page →
| From | Kara M'bola <maxupixu@in.val.it> |
|---|---|
| Date | 2019-06-20 08:41 +0000 |
| Message-ID | <slrnqgmhm8.1as.maxupixu@pisces.home> |
| In reply to | #27313 |
Thu, 20 Jun 2019 07:05:13 +0200, Georges wrote: > Le 20/06/2019 à 06:49, Kara M'bola a écrit : >> Wed, 19 Jun 2019 23:05:27 +0200, Carlos E.R. wrote: >>> >>> Sure, when you already know that it is 20 chars or 20 words in one >>> direction. I never know, I would have to count them. If I see the point, >>> I click the mouse at it. >> >> There's a plugin called vim-easymotion, which solves this problem. With >> "map <space> <Plug>(easymotion-s2)" in your ~/.vimrc hitting space and >> two target characters will take you quickly anywhere on the screen. >> > > ;) seems to be an hlsearch with plugin... > Yeah, pretty much. It obviously has more stuff baked in, some useful, some not as much. Still, I find it pretty handy. It's one of those things you get used to and miss if they're not present. -- :q!
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-20 12:21 +0200 |
| Message-ID | <qefmo3$18ev$1@gioia.aioe.org> |
| In reply to | #27315 |
Le 20/06/2019 à 10:41, Kara M'bola a écrit : > Thu, 20 Jun 2019 07:05:13 +0200, Georges wrote: >> Le 20/06/2019 à 06:49, Kara M'bola a écrit : >>> Wed, 19 Jun 2019 23:05:27 +0200, Carlos E.R. wrote: >>>> >>>> Sure, when you already know that it is 20 chars or 20 words in one >>>> direction. I never know, I would have to count them. If I see the point, >>>> I click the mouse at it. >>> >>> There's a plugin called vim-easymotion, which solves this problem. With >>> "map <space> <Plug>(easymotion-s2)" in your ~/.vimrc hitting space and >>> two target characters will take you quickly anywhere on the screen. >>> >> >> ;) seems to be an hlsearch with plugin... >> > > Yeah, pretty much. It obviously has more stuff baked in, some useful, some > not as much. Still, I find it pretty handy. > It's one of those things you > get used to and miss if they're not present. > Yes... I understand that ;) same for me with some (unix/linux)vim from friends... I get lost without dictionaries and spell-checking in vim ;) -- () /\
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2019-06-19 21:45 -0400 |
| Message-ID | <qeeof9$qbr$1@dont-email.me> |
| In reply to | #27284 |
owl <owl@rooftop.invalid> writes: > Yep. '8w' is more efficient than '40l' for a guess at jumping to a word > near the middle of a line, and definitely more efficient than > 'llllllllllllllllllllllllllllllllllllllll' Actually, all those "l"s are one keystroke. Assuming you've let your keyboard do auto-repeat. Looks like 1 keystroke vs 2 or 3. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-20 03:23 +0000 |
| Message-ID | <suz7993g.vgui4@rooftop.invalid> |
| In reply to | #27302 |
In comp.os.linux.misc Dan Espen <dan1espen@gmail.com> wrote: > owl <owl@rooftop.invalid> writes: > >> Yep. '8w' is more efficient than '40l' for a guess at jumping to a word >> near the middle of a line, and definitely more efficient than >> 'llllllllllllllllllllllllllllllllllllllll' > > Actually, all those "l"s are one keystroke. > Assuming you've let your keyboard do auto-repeat. > Looks like 1 keystroke vs 2 or 3. > A 1.5-second keystroke. No thanks.
[toc] | [prev] | [next] | [standalone]
| From | Grant Taylor <gtaylor@tnetconsulting.net> |
|---|---|
| Date | 2019-06-19 21:45 -0600 |
| Message-ID | <qeevh7$npv$2@tncsrv09.home.tnetconsulting.net> |
| In reply to | #27302 |
On 6/19/19 7:45 PM, Dan Espen wrote: > Actually, all those "l"s are one keystroke. > Assuming you've let your keyboard do auto-repeat. ~shudder~ the thought of waiting on a keyboard auto-repeat for a large number of letters. Not to mention keeping track of them and not over or under shooting. -- Grant. . . . unix || die
[toc] | [prev] | [next] | [standalone]
| From | Bud Frede <frede@mouse-potato.com> |
|---|---|
| Date | 2019-06-30 09:54 -0400 |
| Message-ID | <0audnZ-v-YuwIoXAnZ2dnUU7-TfNnZ2d@supernews.com> |
| In reply to | #27263 |
"Carlos E.R." <robin_listas@es.invalid> writes: > On 19/06/2019 12.30, Rich wrote: >> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>> j for going down a line? Gosh, keyboards have down keys for decades! >> >> Yes, but if you go back enough decades (1976) they did not: >> >> https://en.wikipedia.org/wiki/ADM-3A#Hardware >> >> Notice what is also printed on the h, j, k, and l keys in the keyboard >> layout at that URL. > > So? This is 2019. In 2019 I still find it advantageous to use the hjkl keys to navigate rather than taking my hand off the home row to press the arrow keys. > > > er > ctrl asdf > xc > > were the equivalent keys in wordstar, and they still work in joe. Not > that I ever use them, even if I remember them. Time enough to change. > > (and wordstar was designed for typists, very widely used by people whose > profession was typing stuff) > > > That the vi help today shows the h j k l keys in its main page shows its > age and obsolescence. Enough to having me running away - and I'm old > enough to having seen it, but the first keyboard I bought around 1984 > had arrows. Verified in my personal museum just now. I know people who still use the wordstar key commands they learned back when they were using DOS. (One of them uses Joe as "jstar") I still use vi (vim) and don't find it to be obsolete. (It's viejo, but not gastado) :-) It may not be to your tastes or may not fit your needs, but it does work well for a lot of people and is hardly obsolete.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-30 20:06 +0200 |
| Message-ID | <daanuf-j92.ln1@Telcontar.valinor> |
| In reply to | #27475 |
On 30/06/2019 15.54, Bud Frede wrote: > "Carlos E.R." <robin_listas@es.invalid> writes: > >> On 19/06/2019 12.30, Rich wrote: >>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>> j for going down a line? Gosh, keyboards have down keys for decades! >>> >>> Yes, but if you go back enough decades (1976) they did not: >>> >>> https://en.wikipedia.org/wiki/ADM-3A#Hardware >>> >>> Notice what is also printed on the h, j, k, and l keys in the keyboard >>> layout at that URL. >> >> So? This is 2019. > > In 2019 I still find it advantageous to use the hjkl keys to navigate > rather than taking my hand off the home row to press the arrow keys. > >> >> >> er >> ctrl asdf >> xc >> >> were the equivalent keys in wordstar, and they still work in joe. Not >> that I ever use them, even if I remember them. Time enough to change. >> >> (and wordstar was designed for typists, very widely used by people whose >> profession was typing stuff) >> >> >> That the vi help today shows the h j k l keys in its main page shows its >> age and obsolescence. Enough to having me running away - and I'm old >> enough to having seen it, but the first keyboard I bought around 1984 >> had arrows. Verified in my personal museum just now. > > I know people who still use the wordstar key commands they learned back > when they were using DOS. (One of them uses Joe as "jstar") > > I still use vi (vim) and don't find it to be > obsolete. (It's viejo, but not gastado) :-) > > It may not be to your tastes or may not fit your needs, but it does work > well for a lot of people and is hardly obsolete. It certainly works :-) What I mean is that telling someone on the start "window" that the keyboard is handled with hjkl "instead" of just using the cursor gives a "funny old" impression to newcommers. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | DecadentLinuxUserNumeroUno@decadence.org |
|---|---|
| Date | 2019-06-19 11:55 +0000 |
| Message-ID | <qed7se$db8$3@gioia.aioe.org> |
| In reply to | #27261 |
Rich <rich@example.invalid> wrote in news:qed2rv$jos$1@dont-email.me: > In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >> j for going down a line? Gosh, keyboards have down keys for >> decades! > > Yes, but if you go back enough decades (1976) they did not: > > https://en.wikipedia.org/wiki/ADM-3A#Hardware > > Notice what is also printed on the h, j, k, and l keys in the > keyboard layout at that URL. > > Remember "NetHack"?
[toc] | [prev] | [next] | [standalone]
| From | DecadentLinuxUserNumeroUno@decadence.org |
|---|---|
| Date | 2019-06-22 13:20 +0000 |
| Message-ID | <qel9u1$5hm$1@gioia.aioe.org> |
| In reply to | #27266 |
DecadentLinuxUserNumeroUno@decadence.org wrote in news:qed7se$db8$3 @gioia.aioe.org: > Rich <rich@example.invalid> wrote in > news:qed2rv$jos$1@dont-email.me: > >> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>> j for going down a line? Gosh, keyboards have down keys for >>> decades! >> >> Yes, but if you go back enough decades (1976) they did not: >> >> https://en.wikipedia.org/wiki/ADM-3A#Hardware >> >> Notice what is also printed on the h, j, k, and l keys in the >> keyboard layout at that URL. >> >> > > Remember "NetHack"? It was used back when there were no cursor keys on keyboard yet as well. "Hack" was actually the original. Still around too! <https://www.nethack.org/> <https://nethackwiki.com/wiki/Main_Page> <https://en.wikipedia.org/wiki/NetHack>
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-18 03:22 +0200 |
| Message-ID | <ovqltf-eja.ln1@Telcontar.valinor> |
| In reply to | #27222 |
On 17/06/2019 23.30, Andreas Kohlbach wrote: > On Mon, 17 Jun 2019 12:41:08 -0000 (UTC), Jasen Betts wrote: >> >> On 2019-06-17, Freenet <pieer@free.fr> wrote: >>>> >>>> (I have never understood why anyone would want to waste their time >>>> learning how to use that Vim crap. Just a foolish venture into >>>> egotistical intellectual chauvinism.) >>> >>> What I hate about it is when I accidentally start it. I then >>> usually have to go and dig around the web to find out how to close >>> it. >> >> indeed that is the one essential vi skill <Esc> : q ! <Enter> > > And that information is missing in the "splash screen" (displayed when > you open vi without a file name). This Red Button should IMO be mentioned. And kill the opportunity of telling a good story about the time you had to hit the power switch because of not knowing how to exit vi, and hear the me toos from the back row? :-D -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Sidney_Kotic <kant@have.it> |
|---|---|
| Date | 2019-06-17 18:25 -0800 |
| Message-ID | <qe9i2u$5h3$1@gioia.aioe.org> |
| In reply to | #27227 |
On 6/17/19 5:22 PM, Carlos E.R. 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 upon a time...it was about the only editor you could be assured to find when you booted the system up single-user mode as root. A statically compiled version of vi, sometimes those pesky run-time libraries aren't there, from there you could fix things enough to bring up it up multi-user and with luck eventually a gui.
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-18 08:30 +0200 |
| Message-ID | <qea0dt$18q$1@gioia.aioe.org> |
| In reply to | #27227 |
Le 18/06/2019 à 03:22, Carlos E.R. a écrit : > On 17/06/2019 23.30, Andreas Kohlbach wrote: >> On Mon, 17 Jun 2019 12:41:08 -0000 (UTC), Jasen Betts wrote: >>> >>> On 2019-06-17, Freenet <pieer@free.fr> wrote: >>>>> >>>>> (I have never understood why anyone would want to waste their time >>>>> learning how to use that Vim crap. Just a foolish venture into >>>>> egotistical intellectual chauvinism.) >>>> >>>> What I hate about it is when I accidentally start it. I then >>>> usually have to go and dig around the web to find out how to close >>>> it. >>> >>> indeed that is the one essential vi skill <Esc> : q ! <Enter> >> >> And that information is missing in the "splash screen" (displayed when >> you open vi without a file name). This Red Button should IMO be mentioned. > > And kill the opportunity of telling a good story about the time you had > to hit the power switch because of not knowing how to exit vi, and hear > the me toos from the back row? :-D > > It might be seen as an escape game... ;) -- () /\
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-18 11:29 +0200 |
| Message-ID | <7hnmtf-0bd.ln1@Telcontar.valinor> |
| In reply to | #27227 |
On 18/06/2019 03.22, Carlos E.R. wrote: > On 17/06/2019 23.30, Andreas Kohlbach wrote: >> On Mon, 17 Jun 2019 12:41:08 -0000 (UTC), Jasen Betts wrote: >>> >>> On 2019-06-17, Freenet <pieer@free.fr> wrote: >>>>> >>>>> (I have never understood why anyone would want to waste their time >>>>> learning how to use that Vim crap. Just a foolish venture into >>>>> egotistical intellectual chauvinism.) >>>> >>>> What I hate about it is when I accidentally start it. I then >>>> usually have to go and dig around the web to find out how to close >>>> it. >>> >>> indeed that is the one essential vi skill <Esc> : q ! <Enter> >> >> And that information is missing in the "splash screen" (displayed when >> you open vi without a file name). This Red Button should IMO be mentioned. > > And kill the opportunity of telling a good story about the time you had > to hit the power switch because of not knowing how to exit vi, and hear > the me toos from the back row? :-D > > Now, how did it happen that I wrote "alt.os.linux.suse" group above? It was supposed to be "alt.os.linux". Ah, I see why now while doing it again. Thunderbird tries to be too clever :-( -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2019-06-18 16:15 -0400 |
| Message-ID | <87sgs6bqgr.fsf@usenet.ankman.de> |
| In reply to | #27233 |
On Tue, 18 Jun 2019 11:29:43 +0200, Carlos E.R. wrote: > > Now, how did it happen that I wrote "alt.os.linux.suse" group above? It > was supposed to be "alt.os.linux". > > Ah, I see why now while doing it again. Thunderbird tries to be too > clever :-( Because I set a Followup-To: to avoid cross posting. Okay, you put the other groups back. Since SUSE is mentioned one could add the Debian, RedHat, Fedora... groups. Furthermore this might be off topic in any group dealing with Linux since the topic is about and editor running on UNIX and other operating systems too and there should be a group having editors as topic. At least the de.* hierarchy has. -- Andreas
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-18 20:28 +0000 |
| Message-ID | <szv983ffa.vu3@rooftop.invalid> |
| In reply to | #27243 |
In alt.os.linux Andreas Kohlbach <ank@spamfence.net> wrote: > On Tue, 18 Jun 2019 11:29:43 +0200, Carlos E.R. wrote: >> >> Now, how did it happen that I wrote "alt.os.linux.suse" group above? It >> was supposed to be "alt.os.linux". >> >> Ah, I see why now while doing it again. Thunderbird tries to be too >> clever :-( > > Because I set a Followup-To: to avoid cross posting. > > Okay, you put the other groups back. Since SUSE is mentioned one could > add the Debian, RedHat, Fedora... groups. > > Furthermore this might be off topic in any group dealing with Linux since > the topic is about and editor running on UNIX and other operating systems > too and there should be a group having editors as topic. At least the > de.* hierarchy has. Since any discussion of Linux will invariably focus on some utility or other, I don't see how discussing an editor that is commonly used on Linux would be considered off-topic for a Linux group.
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2019-06-18 17:27 -0400 |
| Message-ID | <87h88mbn3w.fsf@usenet.ankman.de> |
| In reply to | #27244 |
On Tue, 18 Jun 2019 20:28:22 +0000 (UTC), owl wrote: > > In alt.os.linux Andreas Kohlbach <ank@spamfence.net> wrote: >> On Tue, 18 Jun 2019 11:29:43 +0200, Carlos E.R. wrote: >>> >>> Now, how did it happen that I wrote "alt.os.linux.suse" group above? It >>> was supposed to be "alt.os.linux". >>> >>> Ah, I see why now while doing it again. Thunderbird tries to be too >>> clever :-( >> >> Because I set a Followup-To: to avoid cross posting. >> >> Okay, you put the other groups back. Since SUSE is mentioned one could >> add the Debian, RedHat, Fedora... groups. >> >> Furthermore this might be off topic in any group dealing with Linux since >> the topic is about and editor running on UNIX and other operating systems >> too and there should be a group having editors as topic. At least the >> de.* hierarchy has. > > Since any discussion of Linux will invariably focus on some utility or > other, I don't see how discussing an editor that is commonly used on > Linux would be considered off-topic for a Linux group. Because vi exists for many operating systems. It's like discussing a problem with the Firefox browser in a Linux group. Where Firefox is available in at least the Linux, UNIX, Windows, iOS, Android or Mac OS or exotic systems like Haiku (formally known as BeOS), where it is known as Bezilla. -- Andreas
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-19 00:04 +0000 |
| Message-ID | <szz9083.ahu3gva4@rooftop.invalid> |
| In reply to | #27245 |
In comp.os.linux.misc Andreas Kohlbach <ank@spamfence.net> wrote: > On Tue, 18 Jun 2019 20:28:22 +0000 (UTC), owl wrote: >> >> In alt.os.linux Andreas Kohlbach <ank@spamfence.net> wrote: >>> On Tue, 18 Jun 2019 11:29:43 +0200, Carlos E.R. wrote: >>>> >>>> Now, how did it happen that I wrote "alt.os.linux.suse" group above? It >>>> was supposed to be "alt.os.linux". >>>> >>>> Ah, I see why now while doing it again. Thunderbird tries to be too >>>> clever :-( >>> >>> Because I set a Followup-To: to avoid cross posting. >>> >>> Okay, you put the other groups back. Since SUSE is mentioned one could >>> add the Debian, RedHat, Fedora... groups. >>> >>> Furthermore this might be off topic in any group dealing with Linux since >>> the topic is about and editor running on UNIX and other operating systems >>> too and there should be a group having editors as topic. At least the >>> de.* hierarchy has. >> >> Since any discussion of Linux will invariably focus on some utility or >> other, I don't see how discussing an editor that is commonly used on >> Linux would be considered off-topic for a Linux group. > > Because vi exists for many operating systems. So do many other utilities. Are you suggesting that any cross-platform software is off-limits, and the only acceptable topics are the kernel and Linux-only utilities? That would make for a desolate newsgroup. > It's like discussing a > problem with the Firefox browser in a Linux group. Where Firefox is > available in at least the Linux, UNIX, Windows, iOS, Android or Mac OS or > exotic systems like Haiku (formally known as BeOS), where it is known as > Bezilla. If a problem exists with the Linux version of any software, it's on-topic in a Linux group, if for no other reason than giving users a heads-up.
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2019-06-18 22:36 -0400 |
| Message-ID | <87ef3qb8s5.fsf@usenet.ankman.de> |
| In reply to | #27250 |
On Wed, 19 Jun 2019 00:04:35 +0000 (UTC), owl wrote: > > In comp.os.linux.misc Andreas Kohlbach <ank@spamfence.net> wrote: >> On Tue, 18 Jun 2019 20:28:22 +0000 (UTC), owl wrote: >>> >>> In alt.os.linux Andreas Kohlbach <ank@spamfence.net> wrote: >>>> On Tue, 18 Jun 2019 11:29:43 +0200, Carlos E.R. wrote: >>>>> >>>>> Now, how did it happen that I wrote "alt.os.linux.suse" group above? It >>>>> was supposed to be "alt.os.linux". >>>>> >>>>> Ah, I see why now while doing it again. Thunderbird tries to be too >>>>> clever :-( >>>> >>>> Because I set a Followup-To: to avoid cross posting. >>>> >>>> Okay, you put the other groups back. Since SUSE is mentioned one could >>>> add the Debian, RedHat, Fedora... groups. >>>> >>>> Furthermore this might be off topic in any group dealing with Linux since >>>> the topic is about and editor running on UNIX and other operating systems >>>> too and there should be a group having editors as topic. At least the >>>> de.* hierarchy has. >>> >>> Since any discussion of Linux will invariably focus on some utility or >>> other, I don't see how discussing an editor that is commonly used on >>> Linux would be considered off-topic for a Linux group. >> >> Because vi exists for many operating systems. > > So do many other utilities. Are you suggesting that any cross-platform > software is off-limits, and the only acceptable topics are the kernel and > Linux-only utilities? That would make for a desolate newsgroup. Am not suggesting anything. I'm just trying to avoid bloat posting non related Linux articles over many (non related) news groups. That might be old fashioned but that's what I am. > If a problem exists with the Linux version of any software, it's on-topic > in a Linux group, if for no other reason than giving users a heads-up. I agree. Well I give up. I will not set any follow-ups in this group in the future. -- Andreas
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-19 10:06 +0200 |
| Message-ID | <l07ptf-2lt.ln1@Telcontar.valinor> |
| In reply to | #27253 |
On 19/06/2019 04.36, Andreas Kohlbach wrote: > On Wed, 19 Jun 2019 00:04:35 +0000 (UTC), owl wrote: >> >> In comp.os.linux.misc Andreas Kohlbach <ank@spamfence.net> wrote: >>> On Tue, 18 Jun 2019 20:28:22 +0000 (UTC), owl wrote: >>>> >>>> In alt.os.linux Andreas Kohlbach <ank@spamfence.net> wrote: >>>>> On Tue, 18 Jun 2019 11:29:43 +0200, Carlos E.R. wrote: >>>>>> >>>>>> Now, how did it happen that I wrote "alt.os.linux.suse" group above? It >>>>>> was supposed to be "alt.os.linux". >>>>>> >>>>>> Ah, I see why now while doing it again. Thunderbird tries to be too >>>>>> clever :-( >>>>> >>>>> Because I set a Followup-To: to avoid cross posting. >>>>> >>>>> Okay, you put the other groups back. Since SUSE is mentioned one could >>>>> add the Debian, RedHat, Fedora... groups. >>>>> >>>>> Furthermore this might be off topic in any group dealing with Linux since >>>>> the topic is about and editor running on UNIX and other operating systems >>>>> too and there should be a group having editors as topic. At least the >>>>> de.* hierarchy has. >>>> >>>> Since any discussion of Linux will invariably focus on some utility or >>>> other, I don't see how discussing an editor that is commonly used on >>>> Linux would be considered off-topic for a Linux group. >>> >>> Because vi exists for many operating systems. >> >> So do many other utilities. Are you suggesting that any cross-platform >> software is off-limits, and the only acceptable topics are the kernel and >> Linux-only utilities? That would make for a desolate newsgroup. Not me. owl: You replied to my post and my quote. > > Am not suggesting anything. I'm just trying to avoid bloat posting non > related Linux articles over many (non related) news groups. That might be > old fashioned but that's what I am. But I think that it is related to Linux, and so do many, it seems. It is not related to Windows. > >> If a problem exists with the Linux version of any software, it's on-topic >> in a Linux group, if for no other reason than giving users a heads-up. > > I agree. > > Well I give up. I will not set any follow-ups in this group in the future. But why then do you remove generic Linux groups from the thread? Because setting up a follow-up header does that. I agree with removing the advocacy/privacy groups, I don't see why they are there. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2019-06-19 16:15 -0400 |
| Message-ID | <87ef3p1gd1.fsf@usenet.ankman.de> |
| In reply to | #27256 |
On Wed, 19 Jun 2019 10:06:13 +0200, Carlos E.R. wrote: > > On 19/06/2019 04.36, Andreas Kohlbach wrote: >> On Wed, 19 Jun 2019 00:04:35 +0000 (UTC), owl wrote: >> >> Am not suggesting anything. I'm just trying to avoid bloat posting non >> related Linux articles over many (non related) news groups. That might be >> old fashioned but that's what I am. > > But I think that it is related to Linux, and so do many, it seems. It is > not related to Windows. Check out <https://www.vim.org/download.php#pc>. | For modern MS-Windows systems (starting with XP) you can simply use | the executable installer [...] I also just subscribed to | comp.editors -Topics related to computerized text editing. which carries about 1000 articles. First from 2012 talking about the Carlotta hurricane. *sigh* But most others are editor related. >>> If a problem exists with the Linux version of any software, it's on-topic >>> in a Linux group, if for no other reason than giving users a heads-up. >> >> I agree. >> >> Well I give up. I will not set any follow-ups in this group in the future. > > But why then do you remove generic Linux groups from the thread? Because > setting up a follow-up header does that. I *just* (yesterday) gave up and not do this anymore. > > I agree with removing the advocacy/privacy groups, I don't see why they > are there. Because there was also the never ending Emacs VS Vi discussion at some point. -- Andreas My random thoughts and comments https://news-commentaries.blogspot.com/
[toc] | [prev] | [next] | [standalone]
Page 8 of 14 — ← Prev page 1 … 6 7 [8] 9 10 … 14 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web