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 5 of 14 — ← Prev page 1 … 3 4 [5] 6 7 … 14 Next page →
| From | John Hasler <jhasler@newsguy.com> |
|---|---|
| Date | 2019-06-21 10:14 -0500 |
| Message-ID | <87blyrrmvt.fsf@dhh.gt.org> |
| In reply to | #27361 |
F. Russell writes: > You are conflating two entirely different things. A text editor is > nowhere near to being a WYSIWYG editor. WYSIWYG -> What You See Is What You Get. With Vim or Emacs what you see on the screen is what you will get when you print the file. Thus they are WYSIWYG. What you mean is that they are not GUI editors because not everything you can do with them is accessible via menus. By that argument no editor is GUI, because the insert character command requires the use of the keyboard. -- John Hasler jhasler@newsguy.com Dancing Horse Hill Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-21 19:09 +0200 |
| Message-ID | <mifvtf-eqa.ln1@Telcontar.valinor> |
| In reply to | #27366 |
On 21/06/2019 17.14, John Hasler wrote: > F. Russell writes: >> You are conflating two entirely different things. A text editor is >> nowhere near to being a WYSIWYG editor. > > WYSIWYG -> What You See Is What You Get. With Vim or Emacs what you see > on the screen is what you will get when you print the file. Thus they > are WYSIWYG. What you mean is that they are not GUI editors because not > everything you can do with them is accessible via menus. > > By that argument no editor is GUI, because the insert character command > requires the use of the keyboard. Doesn't count, same as the cursor keys do not count. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2019-06-21 13:39 -0400 |
| Message-ID | <qej4oa$q6u$1@dont-email.me> |
| In reply to | #27366 |
John Hasler <jhasler@newsguy.com> writes: > F. Russell writes: >> You are conflating two entirely different things. A text editor is >> nowhere near to being a WYSIWYG editor. > > WYSIWYG -> What You See Is What You Get. With Vim or Emacs what you see > on the screen is what you will get when you print the file. Thus they > are WYSIWYG. What you mean is that they are not GUI editors because not > everything you can do with them is accessible via menus. I don't know if the current Emacs menus provide access to everything, but since the Emacs menus are user configurable, they certainly could. > By that argument no editor is GUI, because the insert character command > requires the use of the keyboard. Not sure about vi/gvim, but Emacs allows for multiple fonts and images in it's buffers. You can most certainly display web pages in it's buffers. The line between text editor and WYSIWYG isn't easy to draw. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2019-06-21 11:18 -0400 |
| Message-ID | <qeisfg$9js$1@dont-email.me> |
| In reply to | #27353 |
"Carlos E.R." <robin_listas@es.invalid> writes: > Ah, and there is no one I know capable of writing in columns, except > word processors. Emacs users know, whenever anyone says an editor can't do something, a little Google searching always proves the claim wrong: https://www.gnu.org/software/emacs/manual/html_node/emacs/Two_002dColumn.html :) -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-21 19:10 +0200 |
| Message-ID | <3mfvtf-eqa.ln1@Telcontar.valinor> |
| In reply to | #27365 |
On 21/06/2019 17.18, Dan Espen wrote: > "Carlos E.R." <robin_listas@es.invalid> writes: > >> Ah, and there is no one I know capable of writing in columns, except >> word processors. > > Emacs users know, whenever anyone says an editor can't do something, > a little Google searching always proves the claim wrong: > > https://www.gnu.org/software/emacs/manual/html_node/emacs/Two_002dColumn.html > > :) > So there is one :-) -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-21 19:57 +0000 |
| Message-ID | <cvz89834ag.ahuo343@rooftop.invalid> |
| In reply to | #27369 |
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: > On 21/06/2019 17.18, Dan Espen wrote: >> "Carlos E.R." <robin_listas@es.invalid> writes: >> >>> Ah, and there is no one I know capable of writing in columns, except >>> word processors. >> >> Emacs users know, whenever anyone says an editor can't do something, >> a little Google searching always proves the claim wrong: >> >> https://www.gnu.org/software/emacs/manual/html_node/emacs/Two_002dColumn.html >> >> :) >> > > So there is one :-) > https://streamable.com/e21kh
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-21 23:09 +0200 |
| Message-ID | <jltvtf-8rl.ln1@Telcontar.valinor> |
| In reply to | #27374 |
On 21/06/2019 21.57, owl wrote: > In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >> On 21/06/2019 17.18, Dan Espen wrote: >>> "Carlos E.R." <robin_listas@es.invalid> writes: >>> >>>> Ah, and there is no one I know capable of writing in columns, except >>>> word processors. >>> >>> Emacs users know, whenever anyone says an editor can't do something, >>> a little Google searching always proves the claim wrong: >>> >>> https://www.gnu.org/software/emacs/manual/html_node/emacs/Two_002dColumn.html >>> >>> :) >>> >> >> So there is one :-) >> > > https://streamable.com/e21kh More or less :-) -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2019-06-21 08:17 +0100 |
| Message-ID | <qei0al$kca$1@dont-email.me> |
| In reply to | #27291 |
On 19/06/2019 21:53, Carlos E.R. wrote: > On 19/06/2019 21.23, The Natural Philosopher wrote: >> On 19/06/2019 20:01, Carlos E.R. wrote: >>> On 19/06/2019 20.47, Georges wrote: >>>> Le 19/06/2019 à 20:32, Tauno Voipio a écrit : >>>>> On 19.6.19 11:55, Georges wrote: >>>>>> Le 19/06/2019 à 10:20, Carlos E.R. a écrit : >>> >>> ... >>> >>>>>> if you teach students, you struggle between time and contents (what >>>>>> you >>>>>> can teach on a 20h course for instance), so 'vi' is a good choice >>>>>> because it's widely used... and simple... once you get the >>>>>> philosophy ;) >>>>>> >>>>> >>>>> If you really want to go backward in time, you should use ed, and no >>>>> newer derivatives like ex and vi with family. >>>>> >>>>> My favourite in primitive editors is nano. >>>>> >>>> >>>> Try this with nano... ;) >>>> >>>> Let's consider a file with 2 columns (or more of course), separated with >>>> <space> or <tab> or whatever you want, you need to invert columns : >>>> >>>> aaaaa bbbbb >>>> aaaaa bbbbb >>>> >>>> :1,$s/^\(.*\) \(.*\)$/\2 \1/ >>>> >>>> bbbbb aaaaa >>>> bbbbb aaaaa >>>> >>>> ;) >>>> >>> >>> Jstar (joe) can do that. Switch to vertical block mode, select the >>> rectangle on the left, move to the right. >>> >> in a Wysiwyg I just highlight the text and move it > > I don't know any such editor that can do that in Linux. Of course, I > have not tried all in existence. > > I can not just highlight all the 'b's. As I try, the 'a's in the > previous line gets highlighted. No vertical block mode. I did it in geany easily Obviously it has to be done one line at a time Geny dioes regexp as well > >> >> >> 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 > > I have edited large files on jstar, too. I don't remember the size. Some > editors need to map the entire file in memory, but 100 MB of ram is > doable nowdays. Yesteryear it had to be done on the file almost > directly, in chunks or whatever. > > Oh, yes, I remember the size. I have edited this file: > > -rw-r--r-- 1 root root 54M Apr 8 05:33 /var/lib/pin/ARCHIVES.gz > > when expanded. It has 5268107 lines, but I'm not going to expand it now > to see the size > > -- "The great thing about Glasgow is that if there's a nuclear attack it'll look exactly the same afterwards." Billy Connolly
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-21 13:03 +0200 |
| Message-ID | <f5qutf-bcq.ln1@Telcontar.valinor> |
| In reply to | #27352 |
On 21/06/2019 09.17, The Natural Philosopher wrote: > On 19/06/2019 21:53, Carlos E.R. wrote: >> On 19/06/2019 21.23, The Natural Philosopher wrote: >>> On 19/06/2019 20:01, Carlos E.R. wrote: >>>> On 19/06/2019 20.47, Georges wrote: >>>>> Le 19/06/2019 à 20:32, Tauno Voipio a écrit : >>>>>> On 19.6.19 11:55, Georges wrote: >>>>>>> Le 19/06/2019 à 10:20, Carlos E.R. a écrit : >>>> >>>> ... >>>> >>>>>>> if you teach students, you struggle between time and contents (what >>>>>>> you >>>>>>> can teach on a 20h course for instance), so 'vi' is a good choice >>>>>>> because it's widely used... and simple... once you get the >>>>>>> philosophy ;) >>>>>>> >>>>>> >>>>>> If you really want to go backward in time, you should use ed, and no >>>>>> newer derivatives like ex and vi with family. >>>>>> >>>>>> My favourite in primitive editors is nano. >>>>>> >>>>> >>>>> Try this with nano... ;) >>>>> >>>>> Let's consider a file with 2 columns (or more of course), separated >>>>> with >>>>> <space> or <tab> or whatever you want, you need to invert columns : >>>>> >>>>> aaaaa bbbbb >>>>> aaaaa bbbbb >>>>> >>>>> :1,$s/^\(.*\) \(.*\)$/\2 \1/ >>>>> >>>>> bbbbb aaaaa >>>>> bbbbb aaaaa >>>>> >>>>> ;) >>>>> >>>> >>>> Jstar (joe) can do that. Switch to vertical block mode, select the >>>> rectangle on the left, move to the right. >>>> >>> in a Wysiwyg I just highlight the text and move it >> >> I don't know any such editor that can do that in Linux. Of course, I >> have not tried all in existence. >> >> I can not just highlight all the 'b's. As I try, the 'a's in the >> previous line gets highlighted. No vertical block mode. > > I did it in geany easily > > Obviously it has to be done one line at a time Ah, that doesn't count. It has to move the entire column or rectangle at a single operation. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-19 19:51 +0000 |
| Message-ID | <sv899zb3.gan33@rooftop.invalid> |
| In reply to | #27275 |
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: > On 19/06/2019 20.47, Georges wrote: >> Le 19/06/2019 à 20:32, Tauno Voipio a écrit : >>> On 19.6.19 11:55, Georges wrote: >>>> Le 19/06/2019 à 10:20, Carlos E.R. a écrit : > > ... > >>>> if you teach students, you struggle between time and contents (what you >>>> can teach on a 20h course for instance), so 'vi' is a good choice >>>> because it's widely used... and simple... once you get the philosophy ;) >>>> >>> >>> If you really want to go backward in time, you should use ed, and no >>> newer derivatives like ex and vi with family. >>> >>> My favourite in primitive editors is nano. >>> >> >> Try this with nano... ;) >> >> Let's consider a file with 2 columns (or more of course), separated with >> <space> or <tab> or whatever you want, you need to invert columns : >> >> aaaaa bbbbb >> aaaaa bbbbb >> >> :1,$s/^\(.*\) \(.*\)$/\2 \1/ >> >> bbbbb aaaaa >> bbbbb aaaaa >> >> ;) >> > > Jstar (joe) can do that. Switch to vertical block mode, select the > rectangle on the left, move to the right. > Shuffling many columns would seem to be a pain that way.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-19 22:45 +0200 |
| Message-ID | <4hjqtf-70u.ln1@Telcontar.valinor> |
| In reply to | #27282 |
On 19/06/2019 21.51, owl wrote: > In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >> On 19/06/2019 20.47, Georges wrote: >>> Le 19/06/2019 à 20:32, Tauno Voipio a écrit : >>>> On 19.6.19 11:55, Georges wrote: >>>>> Le 19/06/2019 à 10:20, Carlos E.R. a écrit : >> >> ... >> >>>>> if you teach students, you struggle between time and contents (what you >>>>> can teach on a 20h course for instance), so 'vi' is a good choice >>>>> because it's widely used... and simple... once you get the philosophy ;) >>>>> >>>> >>>> If you really want to go backward in time, you should use ed, and no >>>> newer derivatives like ex and vi with family. >>>> >>>> My favourite in primitive editors is nano. >>>> >>> >>> Try this with nano... ;) >>> >>> Let's consider a file with 2 columns (or more of course), separated with >>> <space> or <tab> or whatever you want, you need to invert columns : >>> >>> aaaaa bbbbb >>> aaaaa bbbbb >>> >>> :1,$s/^\(.*\) \(.*\)$/\2 \1/ >>> >>> bbbbb aaaaa >>> bbbbb aaaaa >>> >>> ;) >>> >> >> Jstar (joe) can do that. Switch to vertical block mode, select the >> rectangle on the left, move to the right. >> > > Shuffling many columns would seem to be a pain that way. Sure. But the times I had to do such a thing might be counted with my fingers :-) -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | ruben safir <ruben@mrbrklyn.com> |
|---|---|
| Date | 2019-07-20 19:46 -0400 |
| Message-ID | <qh097q$fje$2@reader2.panix.com> |
| In reply to | #27275 |
On 6/19/19 3:01 PM, Carlos E.R. wrote: > Jstar (joe) can do that. Switch to vertical block mode, select the > rectangle on the left, move to the right. yeah that is fucked up. You need to take you hands off the key board. If I wanted a word processor, I would use open office.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-19 21:00 +0200 |
| Message-ID | <nadqtf-7ho.ln1@Telcontar.valinor> |
| In reply to | #27271 |
On 19/06/2019 20.32, Tauno Voipio wrote: > On 19.6.19 11:55, Georges wrote: >> Le 19/06/2019 à 10:20, Carlos E.R. a écrit : >>> On 16/06/2019 22.58, Georges wrote: ... >> if you teach students, you struggle between time and contents (what you >> can teach on a 20h course for instance), so 'vi' is a good choice >> because it's widely used... and simple... once you get the philosophy ;) >> > > If you really want to go backward in time, you should use ed, and no > newer derivatives like ex and vi with family. Edlin in msdos :-P I once used a printer to edit autoexec.bat or config.sys, with a non-working display. Edlin can do that. That got an rs232 connection going to another computer that would act as emergency display. > > My favourite in primitive editors is nano. > -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2019-06-19 20:20 +0100 |
| Message-ID | <qee1u8$ddk$2@dont-email.me> |
| In reply to | #27274 |
On 19/06/2019 20:00, Carlos E.R. wrote: > > I once used a printer to edit autoexec.bat or config.sys, with a > non-working display. Edlin can do that. That got an rs232 connection > going to another computer that would act as emergency display. > Try writing code on a flexowriter. -- If I had all the money I've spent on drink... ..I'd spend it on drink. Sir Henry (at Rawlinson's End)
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-20 14:43 +0200 |
| Message-ID | <7kbstf-ka3.ln1@Telcontar.valinor> |
| In reply to | #27278 |
On 19/06/2019 21.20, The Natural Philosopher wrote: > On 19/06/2019 20:00, Carlos E.R. wrote: > >> >> I once used a printer to edit autoexec.bat or config.sys, with a >> non-working display. Edlin can do that. That got an rs232 connection >> going to another computer that would act as emergency display. >> > > Try writing code on a flexowriter. <https://en.wikipedia.org/wiki/Friden_Flexowriter> Never used one, before my time. A lab on university was still using cards (already obsolete by 1982), but they modernized before I had to use them. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2019-06-19 16:44 -0400 |
| Message-ID | <87blyt1f0t.fsf@usenet.ankman.de> |
| In reply to | #27271 |
On Wed, 19 Jun 2019 21:32:07 +0300, Tauno Voipio wrote: > > If you really want to go backward in time, you should use ed, and no > newer derivatives like ex and vi with family. It was 1989 and I had to take a crash course for programmable logic controller (using compressed air to move things around) when working at a car manufacturer. Cannot remember why, but somebody suggested to write a summary and have everybody of a group of about 20 get a copy. I suggested to used the IBM PC sitting there idle for the two weeks the course would take. I thought "Yeah, I know the Commodore Amiga and C64 and how to edit documents. A PC cannot be much different". Of course I was wrong. The only editor I found was ed (or ex?), running on MS-DOS who knows what version. I never used such a primitive editor before and had no idea, how to use it. There was no documentation and it took me a while only to figure out how to go into insert-mode. The backspace key would (of course, but little did I know) not work to correct a typo. So I killed the program and restarted it some ten times to edit the document from scratch until I made no typo. Finally a Mannesmann-Tally dot matrix printer could put into action to produce 20 copies. Only recently, while running an Osborne I emulated, I learned how to use these early text editors. Understanding they have different modes, like "insert" or "command". Just like you would find it in vi today. -- Andreas
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-19 22:57 +0200 |
| Message-ID | <07kqtf-hou.ln1@Telcontar.valinor> |
| In reply to | #27289 |
On 19/06/2019 22.44, Andreas Kohlbach wrote: > On Wed, 19 Jun 2019 21:32:07 +0300, Tauno Voipio wrote: >> >> If you really want to go backward in time, you should use ed, and no >> newer derivatives like ex and vi with family. > > It was 1989 and I had to take a crash course for programmable logic > controller (using compressed air to move things around) when working at a > car manufacturer. Cannot remember why, but somebody suggested to write a > summary and have everybody of a group of about 20 get a copy. I suggested > to used the IBM PC sitting there idle for the two weeks the course would > take. > > I thought "Yeah, I know the Commodore Amiga and C64 and how to edit > documents. A PC cannot be much different". Of course I was wrong. The > only editor I found was ed (or ex?), running on MS-DOS who knows what > version. I never used such a primitive editor before and had no idea, how > to use it. There was no documentation and it took me a while only to > figure out how to go into insert-mode. The backspace key would (of > course, but little did I know) not work to correct a typo. So I killed > the program and restarted it some ten times to edit the document from > scratch until I made no typo. Finally a Mannesmann-Tally dot matrix > printer could put into action to produce 20 copies. > > Only recently, while running an Osborne I emulated, I learned how to use > these early text editors. Understanding they have different modes, like > "insert" or "command". Just like you would find it in vi today. I don't remember using "ed" in msdos, but surely it would have "edlin" as well. Unless it was msdos 1 or 2, perhaps. I think 'ed' was for use on batch files... I don't remember. I started with dos 3.20. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Wildman <best_lay@yahoo.com> |
|---|---|
| Date | 2019-06-19 16:17 -0500 |
| Message-ID | <44ydnUGwJqwcO5fAnZ2dnUU7-IudnZ2d@giganews.com> |
| In reply to | #27292 |
On Wed, 19 Jun 2019 22:57:36 +0200, Carlos E.R. wrote: > On 19/06/2019 22.44, Andreas Kohlbach wrote: >> On Wed, 19 Jun 2019 21:32:07 +0300, Tauno Voipio wrote: >>> >>> If you really want to go backward in time, you should use ed, and no >>> newer derivatives like ex and vi with family. >> >> It was 1989 and I had to take a crash course for programmable logic >> controller (using compressed air to move things around) when working at a >> car manufacturer. Cannot remember why, but somebody suggested to write a >> summary and have everybody of a group of about 20 get a copy. I suggested >> to used the IBM PC sitting there idle for the two weeks the course would >> take. >> >> I thought "Yeah, I know the Commodore Amiga and C64 and how to edit >> documents. A PC cannot be much different". Of course I was wrong. The >> only editor I found was ed (or ex?), running on MS-DOS who knows what >> version. I never used such a primitive editor before and had no idea, how >> to use it. There was no documentation and it took me a while only to >> figure out how to go into insert-mode. The backspace key would (of >> course, but little did I know) not work to correct a typo. So I killed >> the program and restarted it some ten times to edit the document from >> scratch until I made no typo. Finally a Mannesmann-Tally dot matrix >> printer could put into action to produce 20 copies. >> >> Only recently, while running an Osborne I emulated, I learned how to use >> these early text editors. Understanding they have different modes, like >> "insert" or "command". Just like you would find it in vi today. > > I don't remember using "ed" in msdos, but surely it would have "edlin" > as well. Unless it was msdos 1 or 2, perhaps. I think 'ed' was for use > on batch files... I don't remember. I started with dos 3.20. I could be wrong but I don't think ed was ever released for DOS. Edlin was written by Patterson in 1980 and was part of 86-DOS (QDOS) that was purchased by MS. It was included with every version of MSDOS from up to and including 5. Legend has it that edlin was inspired by ed. -- <Wildman> GNU/Linux user #557453 The cow died so I don't need your bull!
[toc] | [prev] | [next] | [standalone]
| From | Andreas Kohlbach <ank@spamfence.net> |
|---|---|
| Date | 2019-06-19 17:43 -0400 |
| Message-ID | <87lfxxz1wi.fsf@usenet.ankman.de> |
| In reply to | #27294 |
On Wed, 19 Jun 2019 16:17:53 -0500, Wildman wrote: > > On Wed, 19 Jun 2019 22:57:36 +0200, Carlos E.R. wrote: > >> I don't remember using "ed" in msdos, but surely it would have "edlin" >> as well. Unless it was msdos 1 or 2, perhaps. I think 'ed' was for use >> on batch files... I don't remember. I started with dos 3.20. > > I could be wrong but I don't think ed was ever released for > DOS. > > Edlin was written by Patterson in 1980 and was part of 86-DOS > (QDOS) that was purchased by MS. It was included with every > version of MSDOS from up to and including 5. Legend has it > that edlin was inspired by ed. Suppose I though of ed for CP/M and on MS-DOS it was in fact edlin I used. -- Andreas
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-20 00:58 +0200 |
| Message-ID | <69rqtf-3j4.ln1@Telcontar.valinor> |
| In reply to | #27296 |
On 19/06/2019 23.43, Andreas Kohlbach wrote: > On Wed, 19 Jun 2019 16:17:53 -0500, Wildman wrote: >> >> On Wed, 19 Jun 2019 22:57:36 +0200, Carlos E.R. wrote: >> >>> I don't remember using "ed" in msdos, but surely it would have "edlin" >>> as well. Unless it was msdos 1 or 2, perhaps. I think 'ed' was for use >>> on batch files... I don't remember. I started with dos 3.20. >> >> I could be wrong but I don't think ed was ever released for >> DOS. >> >> Edlin was written by Patterson in 1980 and was part of 86-DOS >> (QDOS) that was purchased by MS. It was included with every >> version of MSDOS from up to and including 5. Legend has it >> that edlin was inspired by ed. > > Suppose I though of ed for CP/M and on MS-DOS it was in fact edlin I used. I think there was an ed, that did the role of "sed" in Linux, but less powerful. Edlin was usable as editor, but it was a "line editor", not suitable for a letter. I don't think it would do "wrap", but I don't remember. Its role were config or batch files. I stopped firefox for today, I need the ram for a virtual machine, or I'd check the wikipedia. Maybe it says. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
Page 5 of 14 — ← Prev page 1 … 3 4 [5] 6 7 … 14 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web