Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #206560 > unrolled thread

text editors

Started bymick crane <mick.crane@gmail.com>
First post2019-03-25 05:40 +0100
Last post2019-03-30 12:20 +0100
Articles 18 on this page of 118 — 29 participants

Back to article view | Back to linux.debian.user


Contents

  text editors mick crane <mick.crane@gmail.com> - 2019-03-25 05:40 +0100
    Re: text editors Cindy-Sue Causey <butterflybytes@gmail.com> - 2019-03-25 06:00 +0100
      Re: text editors Jude DaShiell <jdashiel@panix.com> - 2019-03-25 06:10 +0100
    Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-25 06:40 +0100
      Re: text editors mick crane <mick.crane@gmail.com> - 2019-03-25 09:00 +0100
        Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-25 11:20 +0100
          Re: text editors mick crane <mick.crane@gmail.com> - 2019-03-25 11:40 +0100
    Re: text editors Dan Hitt <dan.hitt@gmail.com> - 2019-03-25 07:00 +0100
    Re: text editors john doe <johndoe65534@mail.com> - 2019-03-25 07:40 +0100
    Re: text editors <tomas@tuxteam.de> - 2019-03-25 12:10 +0100
      Re: text editors rhkramer@gmail.com - 2019-03-25 12:50 +0100
        Re: text editors rhkramer@gmail.com - 2019-03-25 13:10 +0100
        Re: text editors Étienne Mollier <etienne.mollier@mailoo.org> - 2019-03-25 21:20 +0100
          Re: text editors deloptes <deloptes@gmail.com> - 2019-03-25 22:10 +0100
    Re: text editors Teemu Likonen <tlikonen@iki.fi> - 2019-03-25 13:30 +0100
      Re: text editors mick crane <mick.crane@gmail.com> - 2019-03-26 08:40 +0100
        Re: text editors Teemu Likonen <tlikonen@iki.fi> - 2019-03-26 16:50 +0100
          Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-26 18:00 +0100
            Re: text editors Håkon Alstadheim <hakon@alstadheim.priv.no> - 2019-03-26 21:20 +0100
            Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-27 03:30 +0100
              Re: text editors rhkramer@gmail.com - 2019-03-27 13:10 +0100
                Re: text editors <tomas@tuxteam.de> - 2019-03-27 14:30 +0100
                  Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-27 15:10 +0100
                    Re: text editors <tomas@tuxteam.de> - 2019-03-27 15:40 +0100
                      Re: text editors rlharris@oplink.net - 2019-03-27 17:30 +0100
                        Re: text editors rlharris@oplink.net - 2019-03-28 18:40 +0100
                          keyboard macros (was: Re: text editors) rhkramer@gmail.com - 2019-03-28 19:00 +0100
                            Re: keyboard macros John Hasler <jhasler@newsguy.com> - 2019-03-28 19:30 +0100
                              Re: keyboard macros Cindy-Sue Causey <butterflybytes@gmail.com> - 2019-03-28 20:00 +0100
                            Re: keyboard macros rlharris@oplink.net - 2019-03-28 19:50 +0100
                              Re: keyboard macros John Hasler <jhasler@newsguy.com> - 2019-03-28 20:10 +0100
                                xfce launchers rlharris@oplink.net - 2019-04-03 18:40 +0200
                                  Re: xfce launchers Mike Kupfer <mkupfer@alum.berkeley.edu> - 2019-04-04 07:20 +0200
                                    Re: xfce launchers rlharris@oplink.net - 2019-04-04 07:40 +0200
                          Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-29 06:20 +0100
                      Re: text editors deloptes <deloptes@gmail.com> - 2019-03-28 03:40 +0100
                        Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-28 03:50 +0100
                          Re: text editors deloptes <deloptes@gmail.com> - 2019-03-28 08:00 +0100
                            Re: text editors <tomas@tuxteam.de> - 2019-03-28 09:20 +0100
                              Re: text editors <tomas@tuxteam.de> - 2019-03-28 10:40 +0100
                              Re: text editors deloptes <deloptes@gmail.com> - 2019-03-28 21:10 +0100
                                Emacs without knowing any Lisp (was: text editors) Ben Finney <bignose@debian.org> - 2019-03-29 02:50 +0100
                                  Re: Emacs without knowing any Lisp (was: text editors) Bill Wood <william.wood3@comcast.net> - 2019-03-29 06:50 +0100
                            Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-28 14:10 +0100
                              Re: text editors <tomas@tuxteam.de> - 2019-03-28 14:50 +0100
                            Re: text editors David Wright <deblis@lionunicorn.co.uk> - 2019-03-28 14:30 +0100
                              Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-28 15:20 +0100
                                Re: text editors <tomas@tuxteam.de> - 2019-03-28 15:30 +0100
                                Re: text editors deloptes <deloptes@gmail.com> - 2019-03-28 21:30 +0100
                                  Re: text editors deloptes <deloptes@gmail.com> - 2019-03-29 00:40 +0100
                                  Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-29 06:30 +0100
                                    Re: text editors Teemu Likonen <tlikonen@iki.fi> - 2019-03-29 09:00 +0100
                                    Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-29 10:20 +0100
                                      Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-29 12:40 +0100
                                    Re: text editors Stefan Monnier <monnier@iro.umontreal.ca> - 2019-03-29 18:00 +0100
                                    Re: text editors deloptes <deloptes@gmail.com> - 2019-03-29 19:50 +0100
                                      Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-29 20:10 +0100
                                        Re: text editors deloptes <deloptes@gmail.com> - 2019-03-30 00:10 +0100
                                          Re: text editors Gene Heskett <gheskett@shentel.net> - 2019-03-30 00:30 +0100
                                            Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-30 01:20 +0100
                                              Re: text editors deloptes <deloptes@gmail.com> - 2019-03-30 01:40 +0100
                                                Re: text editors David Wright <deblis@lionunicorn.co.uk> - 2019-03-30 04:30 +0100
                                                  Re: text editors deloptes <deloptes@gmail.com> - 2019-03-30 09:30 +0100
                                                    What does all this mean? was Re: text editors David Wright <deblis@lionunicorn.co.uk> - 2019-03-30 17:20 +0100
                                                Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-30 05:30 +0100
                                              Re: text editors Bob Bernstein <poobah@ruptured-duck.com> - 2019-03-30 02:20 +0100
                                                Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-30 02:30 +0100
                                            Re: text editors David Wright <deblis@lionunicorn.co.uk> - 2019-03-30 01:50 +0100
                                      Re: text editors deloptes <deloptes@gmail.com> - 2019-04-01 12:10 +0200
                                        Re: text editors <tomas@tuxteam.de> - 2019-04-01 12:10 +0200
                                          Re: text editors Gene Heskett <gheskett@shentel.net> - 2019-04-01 12:50 +0200
                                            Re: text editors David Wright <deblis@lionunicorn.co.uk> - 2019-04-01 16:40 +0200
                                          Re: text editors Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-04-01 16:00 +0200
                                            Re: text editors "Thomas Schmitt" <scdbackup@gmx.net> - 2019-04-01 16:30 +0200
                                              Re: text editors deloptes <deloptes@gmail.com> - 2019-04-01 16:50 +0200
                                              Re: text editors Curt <curty@free.fr> - 2019-04-01 17:40 +0200
                                              Re: text editors Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-04-01 18:20 +0200
                                                Re: text editors "Thomas Schmitt" <scdbackup@gmx.net> - 2019-04-01 19:50 +0200
                                              Re: text editors John Hasler <jhasler@newsguy.com> - 2019-04-01 18:40 +0200
                                          Re: text editors deloptes <deloptes@gmail.com> - 2019-04-01 16:50 +0200
                                            Re: text editors <tomas@tuxteam.de> - 2019-04-01 17:10 +0200
                                  Re: text editors deloptes <deloptes@gmail.com> - 2019-03-29 11:00 +0100
                                    Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-29 13:00 +0100
                            Re: text editors deloptes <deloptes@gmail.com> - 2019-03-28 21:20 +0100
                              Re: text editors deloptes <deloptes@gmail.com> - 2019-03-29 10:50 +0100
                                Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-29 11:50 +0100
                          Re: text editors David Wright <deblis@lionunicorn.co.uk> - 2019-03-28 17:20 +0100
                            Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-28 17:50 +0100
                              Re: text editors Curt <curty@free.fr> - 2019-03-28 18:20 +0100
                            Re: text editors Dekks Herton <dekkzz78@gmail.com> - 2019-03-29 10:40 +0100
                              Re: text editors David Wright <deblis@lionunicorn.co.uk> - 2019-03-29 20:30 +0100
                                Re: text editors Jude DaShiell <jdashiel@panix.com> - 2019-03-30 03:20 +0100
                                Re: text editors David Wright <deblis@lionunicorn.co.uk> - 2019-04-01 18:40 +0200
                            Re: text editors Dekks Herton <dekkzz78@gmail.com> - 2019-03-29 10:40 +0100
                Re: text editors Teemu Likonen <tlikonen@iki.fi> - 2019-03-27 20:40 +0100
                Re: text editors Stefan Monnier <monnier@iro.umontreal.ca> - 2019-03-28 01:30 +0100
            Re: text editors Dan Purgert <dan@djph.net> - 2019-03-27 12:10 +0100
              Re: text editors Teemu Likonen <tlikonen@iki.fi> - 2019-03-28 07:30 +0100
                Re: text editors <tomas@tuxteam.de> - 2019-03-28 11:40 +0100
                  Re: text editors "tomas@tuxteam.de" <tomas@tuxteam.de> - 2019-03-28 12:30 +0100
                    Re: text editors "tomas@tuxteam.de" <tomas@tuxteam.de> - 2019-03-28 13:00 +0100
                  Re: text editors Pierre Fourès <pierre.foures@gmail.com> - 2019-03-28 17:50 +0100
                    Re: text editors deloptes <deloptes@gmail.com> - 2019-03-28 21:40 +0100
          Re: text editors mick crane <mick.crane@gmail.com> - 2019-03-27 10:00 +0100
            Re: text editors Curt <curty@free.fr> - 2019-03-27 11:20 +0100
            Re: text editors Teemu Likonen <tlikonen@iki.fi> - 2019-03-27 16:50 +0100
      Understanding (some) Lisp (was: Re: text editors) rhkramer@gmail.com - 2019-03-28 17:10 +0100
        Re: Understanding (some) Lisp Teemu Likonen <tlikonen@iki.fi> - 2019-03-28 17:20 +0100
    Re: text editors Ben Finney <bignose@debian.org> - 2019-03-26 03:30 +0100
      Re: text editors Teemu Likonen <tlikonen@iki.fi> - 2019-03-26 06:30 +0100
    Re: text editors Tony Rowe <ay986@chebucto.ns.ca> - 2019-03-26 23:40 +0100
      Re: text editors Stefan Monnier <monnier@iro.umontreal.ca> - 2019-03-28 01:30 +0100
        Re: text editors John Hasler <jhasler@newsguy.com> - 2019-03-28 03:00 +0100
        Re: text editors <tomas@tuxteam.de> - 2019-03-28 09:20 +0100
    Re: text editors mick crane <mick.crane@gmail.com> - 2019-03-27 12:10 +0100
      Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-29 07:30 +0100
        Re: text editors Erik Christiansen <dvalin@internode.on.net> - 2019-03-29 09:30 +0100
          Re: text editors mick crane <mick.crane@gmail.com> - 2019-03-30 12:20 +0100

Page 6 of 6 — ← Prev page 1 2 3 4 5 [6]


#206729

From"tomas@tuxteam.de" <tomas@tuxteam.de>
Date2019-03-28 13:00 +0100
Message-ID<xGBRn-5dv-1@gated-at.bofh.it>
In reply to#206726

[Multipart message — attachments visible in raw view] — view raw

On Thu, Mar 28, 2019 at 11:47:02AM +0000, Gian Uberto Lauri wrote:

[snipped the big CC list, probably unintentional]

> In Italian, sudo means "I sweat" :)

In Spanish too: perhaps that's why I like it.
I long for summers...

Cheers
-- t

[toc] | [prev] | [next] | [standalone]


#206743

FromPierre Fourès <pierre.foures@gmail.com>
Date2019-03-28 17:50 +0100
Message-ID<xGGo1-80s-1@gated-at.bofh.it>
In reply to#206724
Le jeu. 28 mars 2019 à 11:32, <tomas@tuxteam.de> a écrit :
>
> If you find that interesting...
>
> imagine you're running your emacs (as a server) and want to
> [...]
>
> Bam :-)
>
> So there are many nifty things in Emacs. But the real killer
> is the integration of all those nifty things.
>

Wow, this gave me the desire to give a real serious try to Emacs !

[toc] | [prev] | [next] | [standalone]


#206761

Fromdeloptes <deloptes@gmail.com>
Date2019-03-28 21:40 +0100
Message-ID<xGJYB-1Op-3@gated-at.bofh.it>
In reply to#206743
Pierre Fourès wrote:

>> So there are many nifty things in Emacs. But the real killer
>> is the integration of all those nifty things.
>>
> 
> Wow, this gave me the desire to give a real serious try to Emacs !

Don't sell your soul to the devil (jokingly) :D

[toc] | [prev] | [next] | [standalone]


#206652

Frommick crane <mick.crane@gmail.com>
Date2019-03-27 10:00 +0100
Message-ID<xGczE-6s2-11@gated-at.bofh.it>
In reply to#206629
On 2019-03-26 15:48, Teemu Likonen wrote:
> mick crane [2019-03-26 07:35:11Z] wrote:
> 
>> there it is then, although I've so far managed to avoid Emacs since
>> heard it is more of an operating system than an editor.
> 
> There are those who know Emacs, and there are those who know decades 
> old
> jokes about Emacs.

Sorry if appeared disrespectful, avoided because seemed daunting. I have 
enough trouble working out what to type as well as how to type it.

mick
-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]


#206653

FromCurt <curty@free.fr>
Date2019-03-27 11:20 +0100
Message-ID<xGdP4-7mG-5@gated-at.bofh.it>
In reply to#206652
On 2019-03-27, mick crane <mick.crane@gmail.com> wrote:
> On 2019-03-26 15:48, Teemu Likonen wrote:
>> mick crane [2019-03-26 07:35:11Z] wrote:
>> 
>>> there it is then, although I've so far managed to avoid Emacs since
>>> heard it is more of an operating system than an editor.
>> 
>> There are those who know Emacs, and there are those who know decades 
>> old
>> jokes about Emacs.
>
> Sorry if appeared disrespectful, avoided because seemed daunting. I have 
> enough trouble working out what to type as well as how to type it.

Some men grow quite intimate with their text editor, and the thing is
right now she must be feeling insulted. Apparently, this middle-aged
lady's sensitive as hell and hasn't been out of the house in decades.
Careful, Mick, because the old hackers from way back she counts as
suitors like showing their teeth in a proprietary, protective reflex (if
they have any left).

Mind you, I'd give the dame a whirl myself (I'm currently stuck in a
rudimentary kind of liaison with Vim), but she wants eleven other
relations to move in with her!

> mick


-- 
“Let us again pretend that life is a solid substance, shaped like a globe,
which we turn about in our fingers. Let us pretend that we can make out a plain
and logical story, so that when one matter is despatched--love for instance--
we go on, in an orderly manner, to the next.” - Virginia Woolf, The Waves

[toc] | [prev] | [next] | [standalone]


#206675

FromTeemu Likonen <tlikonen@iki.fi>
Date2019-03-27 16:50 +0100
Message-ID<xGiYp-1S5-1@gated-at.bofh.it>
In reply to#206652

[Multipart message — attachments visible in raw view] — view raw

mick crane [2019-03-27 08:49:45Z] wrote:

> Sorry if appeared disrespectful, avoided because seemed daunting. I have
> enough trouble working out what to type as well as how to type it.

No problem at all. I have used the very same joke myself a couple of
years ago when I wrote an article to a Finnish computer magazine.
English translation of the title would be "GNU Emacs - a text editor or
an operating system". The article was serious and technical though.

I just find it funny that decades go by and the same jokes are told
again and again. I also think that it is good idea to update oneself.
Emacs has seen a lot of updates too so perhaps maybe people can be
updated too. :-)

-- 
/// Teemu Likonen   - .-..   <https://keybase.io/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///

[toc] | [prev] | [next] | [standalone]


#206739 — Understanding (some) Lisp (was: Re: text editors)

Fromrhkramer@gmail.com
Date2019-03-28 17:10 +0100
SubjectUnderstanding (some) Lisp (was: Re: text editors)
Message-ID<xGFLk-7N4-7@gated-at.bofh.it>
In reply to#206580
<Intentionally top posting -- I think it works better for this case...>

As an exercise for myself (having once had to "learn" Lisp in school, and more 
than once having tried to learn to use EMACS (before the days of the mouse and 
menu, iirc)), I decided to see if I could understand any of the code.

I think I got the gist of most of it, but I don't understand why the double 
parenthesis around "((inhibit-read-only t))"?

On Monday, March 25, 2019 08:29:17 AM Teemu Likonen wrote:
> GNU Emacs has text properties which can be added to any piece of text.
> One of the properties is named "read-only". I made two functions to
> handle the situation you described.
> 
> Put these function to you Emacs's init file (~/.emacs or
> ~/.emacs.d/init.el):
> 
> 
>     (defun read-only-region (beg end)
>       "Makes a region in the current buffer read only, from buffer
>     position BEG to END. If this function is called interactively use
>     the current hightlighted region."
>       (interactive "r")
>       (add-text-properties beg end '(read-only t)))
> 
>     (defun remove-read-only ()
>       "Remove all read only text properties from the current buffer."
>       (interactive)
>       (let ((inhibit-read-only t))
>         (remove-text-properties (point-min) (point-max)
>                                 '(read-only t))))
> 
> 
> Select some text in a buffer and execute command "Alt+x
> read-only-region". That area becomes read only. To remove all read only
> text areas from the current buffer execute command "Alt+x
> remove-read-only".

[toc] | [prev] | [next] | [standalone]


#206740 — Re: Understanding (some) Lisp

FromTeemu Likonen <tlikonen@iki.fi>
Date2019-03-28 17:20 +0100
SubjectRe: Understanding (some) Lisp
Message-ID<xGFUZ-7Qt-1@gated-at.bofh.it>
In reply to#206739

[Multipart message — attachments visible in raw view] — view raw

rhkramer@gmail.com [2019-03-28 12:00:44-04] wrote:

> I think I got the gist of most of it, but I don't understand why the
> double parenthesis around "((inhibit-read-only t))"?

"let" is a special operator which creates new variable bindings. The
syntax is like this:

    (let list-of-variable-bindings
      code-forms)

And each bindings is in the form of (variable value):

    (let ((variable1 value1)
          (variable2 value2)
          (variable3 value3)
          ;; ...
          (variable-n value-n))
      ;; Code that may use those variable bindings.
      )

So logically if there is only one variable binding it looks like this:

    (let ((variable value))
      ;; code
      )

Here's a link to Common Lisp specification about LET and LET* special
operator. Emacs Lisp is different Lisp dialect but it's often quite
close to Common Lisp.

http://www.lispworks.com/documentation/HyperSpec/Body/s_let_l.htm

-- 
/// Teemu Likonen   - .-..   <https://keybase.io/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///

[toc] | [prev] | [next] | [standalone]


#206597

FromBen Finney <bignose@debian.org>
Date2019-03-26 03:30 +0100
Message-ID<xFK0F-61x-1@gated-at.bofh.it>
In reply to#206560
mick crane <mick.crane@gmail.com> writes:

> Is there any text editor, preferably in a terminal that has the
> facility to protect lines in the document, not the document itself ?

If by “protect” you mean “prevent editing these lines but not others”,
no I think that's not a feature of any editor I know.

You can achieve some protection by temporarily *hiding* lines you're not
wanting to edit.

Vim has “folding” (hiding a set of lines).

Emacs has “narrow&"9 to see nothing *but* a specific range of lines.

> I've got 2 blocks of "code" that look similar and I keep editing the
> wrong one and then it doesn't work.

I would use Emacs “narrow” commands for that; quickly narrow the focus
of the editor to only show me the area I'm meaning to edit, then easily
widen the range when I need to.

-- 
 \              “Ridicule is the only weapon which can be used against |
  `\       unintelligible propositions.” —Thomas Jefferson, 1816-07-30 |
_o__)                                                                  |
Ben Finney

[toc] | [prev] | [next] | [standalone]


#206599

FromTeemu Likonen <tlikonen@iki.fi>
Date2019-03-26 06:30 +0100
Message-ID<xFMOR-7Oc-3@gated-at.bofh.it>
In reply to#206597

[Multipart message — attachments visible in raw view] — view raw

Ben Finney [2019-03-26 13:28:56+11] wrote:

> If by “protect” you mean “prevent editing these lines but not others”,
> no I think that's not a feature of any editor I know.

Emacs has that feature. See the "read-only" text property in the
following manual (info) page:

    (elisp) Special Properties

https://www.gnu.org/software/emacs/manual/html_node/elisp/Special-Properties.html#Special-Properties

In my other message in this thread I showed quick example functions for
(1) making a buffer area read only and (2) removing read only
properties. If someone wants to the functions could be made fancier, for
example with a button that removes the read only status.

-- 
/// Teemu Likonen   - .-..   <https://keybase.io/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///

[toc] | [prev] | [next] | [standalone]


#206644

FromTony Rowe <ay986@chebucto.ns.ca>
Date2019-03-26 23:40 +0100
Message-ID<xG2TD-Fl-9@gated-at.bofh.it>
In reply to#206560
On Tue, Mar 26, 2019 at 03:27:53PM -0400, Wayne Sallee wrote:
> I use vim.
> 

I use crispr!

Tony
(Look, someone had to say it)

[toc] | [prev] | [next] | [standalone]


#206701

FromStefan Monnier <monnier@iro.umontreal.ca>
Date2019-03-28 01:30 +0100
Message-ID<xGr5E-70O-11@gated-at.bofh.it>
In reply to#206644
>> I use vim.
> I use crispr!

I was tempted to try it out, but I heard it only handles
a 4-char alphabet.  How do you handle accents?


        Stefan

[toc] | [prev] | [next] | [standalone]


#206703

FromJohn Hasler <jhasler@newsguy.com>
Date2019-03-28 03:00 +0100
Message-ID<xGsuJ-7Jh-3@gated-at.bofh.it>
In reply to#206701
Stefan writes:
> I was tempted to try it out, but I heard it only handles a 4-char
> alphabet.  How do you handle accents?


Phosphorylation, acetylation, and glycosylation.
-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]


#206716

From<tomas@tuxteam.de>
Date2019-03-28 09:20 +0100
Message-ID<xGyqu-3gK-9@gated-at.bofh.it>
In reply to#206701

[Multipart message — attachments visible in raw view] — view raw

On Wed, Mar 27, 2019 at 08:21:41PM -0400, Stefan Monnier wrote:
> >> I use vim.
> > I use crispr!
> 
> I was tempted to try it out, but I heard it only handles
> a 4-char alphabet.  How do you handle accents?

They just went Unicode ;-)

Cheers

[1] http://science.sciencemag.org/content/363/6429/884.full
-- t

[toc] | [prev] | [next] | [standalone]


#206655

Frommick crane <mick.crane@gmail.com>
Date2019-03-27 12:10 +0100
Message-ID<xGeBr-7S5-7@gated-at.bofh.it>
In reply to#206560
On 2019-03-26 19:27, Wayne Sallee wrote:
> I use vim.
> 
> Log in as user that will use vim, and run the following command:
> 
> cat > .vimrc << "EOF"
> set nosi noai
> set number
> 
I have line numbers as the default but copy/paste with the mouse also 
copies the numbers so I have to turn it on and off.

-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]


#206770

FromErik Christiansen <dvalin@internode.on.net>
Date2019-03-29 07:30 +0100
Message-ID<xGTbz-7B7-1@gated-at.bofh.it>
In reply to#206655
On 27.03.19 11:07, mick crane wrote:
> On 2019-03-26 19:27, Wayne Sallee wrote:
> > I use vim.
> > 
> > Log in as user that will use vim, and run the following command:
> > 
> > cat > .vimrc << "EOF"
> > set nosi noai
> > set number
> > 
> I have line numbers as the default but copy/paste with the mouse also copies
> the numbers so I have to turn it on and off.

True, so it's handy to be able to toggle them on and off on a single
keystroke. I use F1, as it is easy to find. This vimscript in .vimrc
then implements the switch, in my case for _relative_ line numbers, as
they allow e.g. y7+ to copy current line plus the lines down to a chosen
point, without having to count the lines. That's a greater productivity
improver than just knowing you're on line 27423:

" Toggle relative line numbering.
function! NList_toggle()
    if &rnu == 1
     set nornu                " For absolute, elide the 'r'.
  else
     set rnu                  " For absolute, elide the 'r'.
  endif
endfun

To avoid stairstepped insert when pasting that here from the clipboard,
I have F12 mapped to:

set pastetoggle=<F12>         " <A-p> is easier. (See "Paste")

I tend to forget that I also have the alternative:

" Paste
" Paste without needing pastetoggle to avoid staircase text, due to ai always set.
" Works with "+y<motion> in another vim instance. Also avoids wrapping.
nnoremap <A-p> "+p
inoremap <A-p> ^["+p^Mi
nnoremap <A-c> "+y

(The ^[ is entered as control-v Esc, and ^M as control-v Enter, but you
knew that.)

<A-p> is Alt-p. Your choice of invoking key may differ.

So, yep, Vim does allow two-key chords, and the distinction from Emacs
reduces a little when you do that. Vimscript may look a little C-like in
places, but that can't be helped. (Awk is also significantly C-like.
Perl is much more successful at voiding the benefit of common language
know-how.)

Erik

[toc] | [prev] | [next] | [standalone]


#206772

FromErik Christiansen <dvalin@internode.on.net>
Date2019-03-29 09:30 +0100
Message-ID<xGV3H-iM-1@gated-at.bofh.it>
In reply to#206770
On 29.03.19 17:26, Erik Christiansen wrote:
> " Toggle relative line numbering.
> function! NList_toggle()
>     if &rnu == 1
>      set nornu                " For absolute, elide the 'r'.
>   else
>      set rnu                  " For absolute, elide the 'r'.
>   endif
> endfun

Apologies. There's almost always something omitted when pasting from
elsewhere. Let's include the connection to the F1 key:

noremap <F1> :call NList_toggle()

A more meaningful function name would be better, too.
(but important here is only the connection, and the toggling, for the
moment.)

Erik

[toc] | [prev] | [next] | [standalone]


#206805

Frommick crane <mick.crane@gmail.com>
Date2019-03-30 12:20 +0100
Message-ID<xHkbM-7p8-7@gated-at.bofh.it>
In reply to#206772
On 2019-03-29 08:22, Erik Christiansen wrote:
> On 29.03.19 17:26, Erik Christiansen wrote:
>> " Toggle relative line numbering.
>> function! NList_toggle()
>>     if &rnu == 1
>>      set nornu                " For absolute, elide the 'r'.
>>   else
>>      set rnu                  " For absolute, elide the 'r'.
>>   endif
>> endfun
> 
> Apologies. There's almost always something omitted when pasting from
> elsewhere. Let's include the connection to the F1 key:
> 
> noremap <F1> :call NList_toggle()
> 
> A more meaningful function name would be better, too.
> (but important here is only the connection, and the toggling, for the
> moment.)
> 
> Erik

thanks for these

mick
-- 
Key ID    4BFEBB31

[toc] | [prev] | [standalone]


Page 6 of 6 — ← Prev page 1 2 3 4 5 [6]

Back to top | Article view | linux.debian.user


csiph-web