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 4 of 14 — ← Prev page 1 2 3 [4] 5 6 … 14 Next page →
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-19 22:53 +0200 |
| Message-ID | <pvjqtf-3hu.ln1@Telcontar.valinor> |
| In reply to | #27279 |
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. > > > 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 -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-19 23:09 +0000 |
| Message-ID | <bvnhs7793qr.ah@rooftop.invalid> |
| In reply to | #27291 |
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. > Vim. > 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. > Vim has Ctrl-v for visual block select. Select a column, then hit 'd' to cut. Move the cursor to wherever and hit 'p' to paste.
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-20 05:21 +0200 |
| Message-ID | <qeeu3e$1th0$1@gioia.aioe.org> |
| In reply to | #27300 |
Le 20/06/2019 à 01:09, owl a écrit : > In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >> > > Vim. > >> 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. >> > > Vim has Ctrl-v for visual block select. Select a column, then hit 'd' > to cut. Move the cursor to wherever and hit 'p' to paste. > Very nice !!! Here is : - select the first char of a column - hit C-v - select the last of the same column => highlight - etc. ;) -- () /\
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-20 04:16 +0000 |
| Message-ID | <scuvz993.agh4u@rooftop.invalid> |
| In reply to | #27304 |
In comp.os.linux.misc Georges <georges@prout.com> wrote: > Le 20/06/2019 à 01:09, owl a écrit : >> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >>> >> >> Vim. >> >>> 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. >>> >> >> Vim has Ctrl-v for visual block select. Select a column, then hit 'd' >> to cut. Move the cursor to wherever and hit 'p' to paste. >> > > Very nice !!! > > Here is : > > - select the first char of a column > - hit C-v > - select the last of the same column => highlight > - etc. > > ;) > :set nosol That will maintain column position for gg (first line) ang G (last line) navigation. Then you can be in a column and just gg<Ctrl-v>G5l an get a five-char wide selection from top to bottom. Or you can have the selection extend to the next space with "f " instead of "5l" or to a tab or whatever. You can record these as a macro into a register, say register b, and then run it on a column with @b for quick and easy column selection. Successfully automating it would depend on column contents of course, but that will give you an idea of the kinds of things that can be done.
[toc] | [prev] | [next] | [standalone]
| From | Georges <georges@prout.com> |
|---|---|
| Date | 2019-06-20 06:21 +0200 |
| Message-ID | <qef1kn$c38$1@gioia.aioe.org> |
| In reply to | #27309 |
Le 20/06/2019 à 06:16, owl a écrit : > In comp.os.linux.misc Georges <georges@prout.com> wrote: >> Le 20/06/2019 à 01:09, owl a écrit : >>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >>>> >>> >>> Vim. >>> >>>> 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. >>>> >>> >>> Vim has Ctrl-v for visual block select. Select a column, then hit 'd' >>> to cut. Move the cursor to wherever and hit 'p' to paste. >>> >> >> Very nice !!! >> >> Here is : >> >> - select the first char of a column >> - hit C-v >> - select the last of the same column => highlight >> - etc. >> >> ;) >> > > :set nosol > That will maintain column position for gg (first line) ang G (last line) > navigation. Then you can be in a column and just gg<Ctrl-v>G5l an get > a five-char wide selection from top to bottom. Or you can have the > selection extend to the next space with "f " instead of "5l" or to > a tab or whatever. You can record these as a macro into a register, > say register b, and then run it on a column with @b for quick and > easy column selection. Successfully automating it would depend on > column contents of course, but that will give you an idea of the > kinds of things that can be done. > > :D very nice of you, works great !!! -- () /\
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-20 14:38 +0200 |
| Message-ID | <tbbstf-ka3.ln1@Telcontar.valinor> |
| In reply to | #27300 |
On 20/06/2019 01.09, owl wrote: > In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >> > > Vim. Doesn't count :-P Not Wysiwyg. >> 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. >> > > Vim has Ctrl-v for visual block select. Select a column, then hit 'd' > to cut. Move the cursor to wherever and hit 'p' to paste. > -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-20 13:30 +0000 |
| Message-ID | <szjbu993ta.ahuo3@rooftop.invalid> |
| In reply to | #27322 |
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: > On 20/06/2019 01.09, owl wrote: >> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >>> >> >> Vim. > > Doesn't count :-P > > Not Wysiwyg. > As plain text editors go, how is vim any less WYSIWYG than any other? If you are referring to mouse support, even terminal vim has it, and mouse-based block-select works in an xterm when you turn on mouse support. And there is also gvim, where it works out of the box.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-20 19:21 +0200 |
| Message-ID | <otrstf-47f.ln1@Telcontar.valinor> |
| In reply to | #27326 |
On 20/06/2019 15.30, owl wrote: > In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >> On 20/06/2019 01.09, owl wrote: >>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >>>> >>> >>> Vim. >> >> Doesn't count :-P >> >> Not Wysiwyg. >> > > As plain text editors go, how is vim any less WYSIWYG than any > other? If you are referring to mouse support, even terminal > vim has it, and mouse-based block-select works in an xterm > when you turn on mouse support. And there is also gvim, where > it works out of the box. Mmmm. Well, I was thinking of GUI editors. Say, kwrite. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-20 18:39 +0000 |
| Message-ID | <svb9z0903ga.h43@rooftop.invalid> |
| In reply to | #27333 |
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: > On 20/06/2019 15.30, owl wrote: >> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>> On 20/06/2019 01.09, owl wrote: >>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >>>>> >>>> >>>> Vim. >>> >>> Doesn't count :-P >>> >>> Not Wysiwyg. >>> >> >> As plain text editors go, how is vim any less WYSIWYG than any >> other? If you are referring to mouse support, even terminal >> vim has it, and mouse-based block-select works in an xterm >> when you turn on mouse support. And there is also gvim, where >> it works out of the box. > > Mmmm. > > Well, I was thinking of GUI editors. Say, kwrite. > https://streamable.com/b1usd
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-20 22:52 +0200 |
| Message-ID | <v88ttf-7vp.ln1@Telcontar.valinor> |
| In reply to | #27336 |
On 20/06/2019 20.39, owl wrote: > In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >> On 20/06/2019 15.30, owl wrote: >>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>> On 20/06/2019 01.09, owl wrote: >>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >>>>>> >>>>> >>>>> Vim. >>>> >>>> Doesn't count :-P >>>> >>>> Not Wysiwyg. >>>> >>> >>> As plain text editors go, how is vim any less WYSIWYG than any >>> other? If you are referring to mouse support, even terminal >>> vim has it, and mouse-based block-select works in an xterm >>> when you turn on mouse support. And there is also gvim, where >>> it works out of the box. >> >> Mmmm. >> >> Well, I was thinking of GUI editors. Say, kwrite. >> > > https://streamable.com/b1usd Ok, but it is a vim variant. gvim2. News to me, not available on openSUSE. And if it follows the vi keyboard, I can't use it. <https://en.wikipedia.org/wiki/Vim_(text_editor)#Interface> *Interface* «Like vi, Vim's interface is not based on menus or icons but on commands given in a text user interface; its GUI mode, gVim, adds menus and toolbars for commonly used commands but the full functionality is still expressed through its command line mode. Vi (and by extension Vim) tends to allow a typist to keep their fingers on the home row, which can be an advantage for a touch typist.[29]» On gvim2, I find nothing. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-20 23:48 +0000 |
| Message-ID | <ugjjxyv62.njb6@rooftop.invalid> |
| In reply to | #27340 |
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: > On 20/06/2019 20.39, owl wrote: >> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>> On 20/06/2019 15.30, owl wrote: >>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>>> On 20/06/2019 01.09, owl wrote: >>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >>>>>>> >>>>>> >>>>>> Vim. >>>>> >>>>> Doesn't count :-P >>>>> >>>>> Not Wysiwyg. >>>>> >>>> >>>> As plain text editors go, how is vim any less WYSIWYG than any >>>> other? If you are referring to mouse support, even terminal >>>> vim has it, and mouse-based block-select works in an xterm >>>> when you turn on mouse support. And there is also gvim, where >>>> it works out of the box. >>> >>> Mmmm. >>> >>> Well, I was thinking of GUI editors. Say, kwrite. >>> >> >> https://streamable.com/b1usd > > Ok, but it is a vim variant. gvim2. News to me, not available on > openSUSE. And if it follows the vi keyboard, I can't use it. > > > <https://en.wikipedia.org/wiki/Vim_(text_editor)#Interface> > > *Interface* > > «Like vi, Vim's interface is not based on menus or icons but on commands > given in a text user interface; its GUI mode, gVim, adds menus and > toolbars for commonly used commands but the full functionality is still > expressed through its command line mode. Vi (and by extension Vim) tends > to allow a typist to keep their fingers on the home row, which can be an > advantage for a touch typist.[29]» > > > On gvim2, I find nothing. > As far as I know the "2" in "gvim2" just means GTK2. There is also a GTK3 version. As for it being a "variant", it's the same vim I use in the terminal. anon@lowtide:~$ ls -l /etc/alternatives/vim lrwxrwxrwx 1 root root 16 Feb 18 09:31 /etc/alternatives/vim -> /usr/bin/vim.gtk anon@lowtide:~$ ls -l /etc/alternatives/gvim lrwxrwxrwx 1 root root 16 Feb 18 09:31 /etc/alternatives/gvim -> /usr/bin/vim.gtk anon@lowtide:~$ The gui can be brought up either with the '-g' switch or by starting as 'gvim'. https://software.opensuse.org/package/gvim
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-21 13:01 +0200 |
| Message-ID | <42qutf-bcq.ln1@Telcontar.valinor> |
| In reply to | #27349 |
On 21/06/2019 01.48, owl wrote: > In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >> On 20/06/2019 20.39, owl wrote: >>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>> On 20/06/2019 15.30, owl wrote: >>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>>>> On 20/06/2019 01.09, owl wrote: >>>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >>>>>>>> >>>>>>> >>>>>>> Vim. >>>>>> >>>>>> Doesn't count :-P >>>>>> >>>>>> Not Wysiwyg. >>>>>> >>>>> >>>>> As plain text editors go, how is vim any less WYSIWYG than any >>>>> other? If you are referring to mouse support, even terminal >>>>> vim has it, and mouse-based block-select works in an xterm >>>>> when you turn on mouse support. And there is also gvim, where >>>>> it works out of the box. >>>> >>>> Mmmm. >>>> >>>> Well, I was thinking of GUI editors. Say, kwrite. >>>> >>> >>> https://streamable.com/b1usd >> >> Ok, but it is a vim variant. gvim2. News to me, not available on >> openSUSE. And if it follows the vi keyboard, I can't use it. >> >> >> <https://en.wikipedia.org/wiki/Vim_(text_editor)#Interface> >> >> *Interface* >> >> «Like vi, Vim's interface is not based on menus or icons but on commands >> given in a text user interface; its GUI mode, gVim, adds menus and >> toolbars for commonly used commands but the full functionality is still >> expressed through its command line mode. Vi (and by extension Vim) tends >> to allow a typist to keep their fingers on the home row, which can be an >> advantage for a touch typist.[29]» >> >> >> On gvim2, I find nothing. >> > > As far as I know the "2" in "gvim2" just means GTK2. There is also > a GTK3 version. As for it being a "variant", it's the same vim > I use in the terminal. > > anon@lowtide:~$ ls -l /etc/alternatives/vim > lrwxrwxrwx 1 root root 16 Feb 18 09:31 /etc/alternatives/vim -> /usr/bin/vim.gtk > anon@lowtide:~$ ls -l /etc/alternatives/gvim > lrwxrwxrwx 1 root root 16 Feb 18 09:31 /etc/alternatives/gvim -> /usr/bin/vim.gtk > anon@lowtide:~$ > > The gui can be brought up either with the '-g' switch or by starting as 'gvim'. > https://software.opensuse.org/package/gvim Ok, then it is just the same as gvim in openSUSE. The thing remains, there is no GUI editor (besides gvim) that can move columns. Joe does, but is not a GUI. Ah, and there is no one I know capable of writing in columns, except word processors. (I do not consider gvim valid Wysiwyg because it does not expose its full command set on the menu, you need the keyboard. On a normal GUI program, first we see the command on some menu, then we learn the shortcut, even if for just a short time.) -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-21 12:30 +0000 |
| Message-ID | <xvu39a3ta.hu4@rooftop.invalid> |
| In reply to | #27353 |
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: > On 21/06/2019 01.48, owl wrote: >> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>> On 20/06/2019 20.39, owl wrote: >>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>>> On 20/06/2019 15.30, owl wrote: >>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>>>>> On 20/06/2019 01.09, owl wrote: >>>>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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. >>>>>>>>> >>>>>>>> >>>>>>>> Vim. >>>>>>> >>>>>>> Doesn't count :-P >>>>>>> >>>>>>> Not Wysiwyg. >>>>>>> >>>>>> >>>>>> As plain text editors go, how is vim any less WYSIWYG than any >>>>>> other? If you are referring to mouse support, even terminal >>>>>> vim has it, and mouse-based block-select works in an xterm >>>>>> when you turn on mouse support. And there is also gvim, where >>>>>> it works out of the box. >>>>> >>>>> Mmmm. >>>>> >>>>> Well, I was thinking of GUI editors. Say, kwrite. >>>>> >>>> >>>> https://streamable.com/b1usd >>> >>> Ok, but it is a vim variant. gvim2. News to me, not available on >>> openSUSE. And if it follows the vi keyboard, I can't use it. >>> >>> >>> <https://en.wikipedia.org/wiki/Vim_(text_editor)#Interface> >>> >>> *Interface* >>> >>> «Like vi, Vim's interface is not based on menus or icons but on commands >>> given in a text user interface; its GUI mode, gVim, adds menus and >>> toolbars for commonly used commands but the full functionality is still >>> expressed through its command line mode. Vi (and by extension Vim) tends >>> to allow a typist to keep their fingers on the home row, which can be an >>> advantage for a touch typist.[29]» >>> >>> >>> On gvim2, I find nothing. >>> >> >> As far as I know the "2" in "gvim2" just means GTK2. There is also >> a GTK3 version. As for it being a "variant", it's the same vim >> I use in the terminal. >> >> anon@lowtide:~$ ls -l /etc/alternatives/vim >> lrwxrwxrwx 1 root root 16 Feb 18 09:31 /etc/alternatives/vim -> /usr/bin/vim.gtk >> anon@lowtide:~$ ls -l /etc/alternatives/gvim >> lrwxrwxrwx 1 root root 16 Feb 18 09:31 /etc/alternatives/gvim -> /usr/bin/vim.gtk >> anon@lowtide:~$ >> >> The gui can be brought up either with the '-g' switch or by starting as 'gvim'. >> https://software.opensuse.org/package/gvim > > Ok, then it is just the same as gvim in openSUSE. > > The thing remains, there is no GUI editor (besides gvim) that can move > columns. Joe does, but is not a GUI. > > Ah, and there is no one I know capable of writing in columns, except > word processors. > Depends on what you mean by writing in columns. https://streamable.com/p6uy6 > > (I do not consider gvim valid Wysiwyg because it does not expose its > full command set on the menu, you need the keyboard. On a normal GUI > program, first we see the command on some menu, then we learn the > shortcut, even if for just a short time.) > > WYSIWYG has nothing to do with command-set exposure. It has to do with the document. And if any text editor can be considered WYSIWYG, then vim can be also.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-21 14:51 +0200 |
| Message-ID | <pe0vtf-ol.ln1@Telcontar.valinor> |
| In reply to | #27357 |
On 21/06/2019 14.30, owl wrote: > In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >> On 21/06/2019 01.48, owl wrote: >>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>> On 20/06/2019 20.39, owl wrote: >>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>>>> On 20/06/2019 15.30, owl wrote: >>>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>>>>>> On 20/06/2019 01.09, owl wrote: >>>>>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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 : >>>>>>>>>>>> >>>>>>>>>>>> ... ... >> The thing remains, there is no GUI editor (besides gvim) that can move >> columns. Joe does, but is not a GUI. >> >> Ah, and there is no one I know capable of writing in columns, except >> word processors. >> > > Depends on what you mean by writing in columns. > https://streamable.com/p6uy6 This is one column flows to the next where I'm writing. column. At some point, text That's one mode, page mode perhaps. > >> >> (I do not consider gvim valid Wysiwyg because it does not expose its >> full command set on the menu, you need the keyboard. On a normal GUI >> program, first we see the command on some menu, then we learn the >> shortcut, even if for just a short time.) >> >> > > WYSIWYG has nothing to do with command-set exposure. It has to do > with the document. And if any text editor can be considered WYSIWYG, > then vim can be also. I refer to this: <https://en.wikipedia.org/wiki/Vim_(text_editor)#Interface> Interface «Like vi, Vim's interface is not based on menus or icons but on commands given in a text user interface; its GUI mode, gVim, adds menus and toolbars for commonly used commands but the full functionality is still expressed through its command line mode. Vi (and by extension Vim) tends to allow a typist to keep their fingers on the home row, which can be an advantage for a touch typist.[29]» So, the full functionality is not accesable via menus... -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-21 13:43 +0000 |
| Message-ID | <s8z08b3ga.yhu3@rooftop.invalid> |
| In reply to | #27358 |
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: > On 21/06/2019 14.30, owl wrote: >> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>> On 21/06/2019 01.48, owl wrote: >>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>>> On 20/06/2019 20.39, owl wrote: >>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>>>>> On 20/06/2019 15.30, owl wrote: >>>>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote: >>>>>>>>> On 20/06/2019 01.09, owl wrote: >>>>>>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> 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 : >>>>>>>>>>>>> >>>>>>>>>>>>> ... > > ... > >>> The thing remains, there is no GUI editor (besides gvim) that can move >>> columns. Joe does, but is not a GUI. >>> >>> Ah, and there is no one I know capable of writing in columns, except >>> word processors. >>> >> >> Depends on what you mean by writing in columns. >> https://streamable.com/p6uy6 > > This is one column flows to the next > where I'm writing. column. > At some point, text > > > That's one mode, page mode perhaps. > A function could probably be created to do that. >> >>> >>> (I do not consider gvim valid Wysiwyg because it does not expose its >>> full command set on the menu, you need the keyboard. On a normal GUI >>> program, first we see the command on some menu, then we learn the >>> shortcut, even if for just a short time.) >>> >>> >> >> WYSIWYG has nothing to do with command-set exposure. It has to do >> with the document. And if any text editor can be considered WYSIWYG, >> then vim can be also. > > I refer to this: > > <https://en.wikipedia.org/wiki/Vim_(text_editor)#Interface> > > Interface > «Like vi, Vim's interface is not based on menus or icons but on commands > given in a text user interface; its GUI mode, gVim, adds menus and > toolbars for commonly used commands but the full functionality is still > expressed through its command line mode. Vi (and by extension Vim) tends > to allow a typist to keep their fingers on the home row, which can be an > advantage for a touch typist.[29]» > > https://en.wikipedia.org/wiki/WYSIWYG > So, the full functionality is not accesable via menus... > Irrelevant. And the full functionality is documented in the menus. Note: a keyboard is needed for some menu-driven functionality in *all* GUI text editors, e.g. a search/replace function.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2019-06-23 12:56 +0200 |
| Message-ID | <gn9469F8hl7U1@mid.individual.net> |
| In reply to | #27362 |
On 21/06/2019 15.43, owl wrote:
> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 21/06/2019 14.30, owl wrote:
>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>>>> On 21/06/2019 01.48, owl wrote:
>>>>> In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
>
> https://en.wikipedia.org/wiki/WYSIWYG
>
>> So, the full functionality is not accesable via menus...
>>
>
> Irrelevant. And the full functionality is documented in the menus.
> Note: a keyboard is needed for some menu-driven functionality in
> *all* GUI text editors, e.g. a search/replace function.
Not all. I don't remember any GUI editor I use where I can not do
search/replace via menu.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <jhasler@newsguy.com> |
|---|---|
| Date | 2019-06-21 08:55 -0500 |
| Message-ID | <87fto3rqk8.fsf@dhh.gt.org> |
| In reply to | #27358 |
Carlos writes: > So, the full functionality is not accesable via menus... So you really want to use Emacs. Using any really powerful program entirely through menus is impractical, though. I use both Emacs and Vim. I rarely touch the menus in Emacs and I've never used Vim in anything but Vi mode (Vi being the first screen editor I learned). -- 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:01 +0200 |
| Message-ID | <34fvtf-haa.ln1@Telcontar.valinor> |
| In reply to | #27363 |
On 21/06/2019 15.55, John Hasler wrote: > Carlos writes: >> So, the full functionality is not accesable via menus... > > So you really want to use Emacs. > > Using any really powerful program entirely through menus is impractical, > though. I use both Emacs and Vim. I rarely touch the menus in Emacs > and I've never used Vim in anything but Vi mode (Vi being the first > screen editor I learned). I know that it is impractical, but that is the way I learn the keyboard interface of any editor. When I have to use Emacs, I start with the menu, then whatever is frequent I use directly. The menu says the shortcut. If gvim has some functionality not accessible from the menu, then it is not useful to me. Wrong approach to me. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | "F. Russell" <frussell@random.info> |
|---|---|
| Date | 2019-06-21 13:33 +0000 |
| Message-ID | <qeimar07hk@news2.newsguy.com> |
| In reply to | #27357 |
On Fri, 21 Jun 2019 12:30:03 +0000, owl vomited this verbiage that I considered to be worthy of my attention for one of a variety of possible reasons: > > WYSIWYG has nothing to do with command-set exposure. It has to do > with the document. And if any text editor can be considered WYSIWYG, > then vim can be also. > You are conflating two entirely different things. A text editor is nowhere near to being a WYSIWYG editor. A text editor does exactly, and only, what the term implies: edit text. That is, a text editor manipulates only bytes that are interpreted as representing text characters. (And no, XML and HTML are NOT considered text files.) A WYSIWYG editor, or word processor, manipulates much information that does NOT represent characters, such as formatting, typeface, margins, line spacing, positioning, etc. The resulting file is essentially binary in nature. A text editor can do a minimal kind of WYSIWYG but only through the judicious use of spacing and tab characters. There is nothing in the resulting file that is not pure text. A text editor cannot do boldface, underlining, italics, etc. and if it does then it is no longer to be classified as a text editor. By the way, the absolute best text editor for GNU/Linux is cooledit. Pound for pound, cooledit will blow anything else out of the water -- and this is true in spite of its relatively antiquated nature and lack of maintenance.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-06-21 13:39 +0000 |
| Message-ID | <sauzx0b083.a@rooftop.invalid> |
| In reply to | #27360 |
In comp.os.linux.misc F. Russell <frussell@random.info> wrote: > On Fri, 21 Jun 2019 12:30:03 +0000, owl vomited this verbiage that I > considered to be worthy of my attention for one of a variety of possible > reasons: > >> >> WYSIWYG has nothing to do with command-set exposure. It has to do >> with the document. And if any text editor can be considered WYSIWYG, >> then vim can be also. >> > > You are conflating two entirely different things. A text editor is > nowhere near to being a WYSIWYG editor. > No, I'm not doing that. I said if *any* text editor can be considered WYSIWYG (and I did not bring in that term with respect to text editors), then vim can.
[toc] | [prev] | [next] | [standalone]
Page 4 of 14 — ← Prev page 1 2 3 [4] 5 6 … 14 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web