schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Search results for tag #vim

[?]Jocelyn » 🌐
@cyclotopie@mastodon.gougere.fr

@daph

C'est exagéré le 2e picto, même en cas de fatigue extrême on fait ZZ et pas ZZZ.

D'ailleurs on lui préfère :wq!

    [?]TelH90 » 🌐
    @kkarhan@mastodon.social

    [?]JdeBP » 🌐
    @JdeBP@tty0.social

    on after I upgraded a Debian machine is coming up with some very poor colours when syntax highlighting is turned on.

    It turns out that the default colour scheme is a lot plainer than it used to be in the days of syncolor.vim. Changing the colour scheme to something non-default like 'shine' shows that the syntax highlighting is all still working. It's just mostly picking from a palette of black and white in the default colour scheme.

      [?]NerdNextDoor :Blobhaj: » 🌐
      @mrmasterkeyboard@mastodon.social

      FINAL EDIT: We've been making good progress with EVi! We've fully settled on version 9.1.0 with no AI code, we're on IRC @ irc.oftc.net, we've gained a lots of popularity and we've been working on fixing tests and removing platforms that are deemed exotic with other cleanups. Thank you to everyone who has supported us this week!!!

      hard-forked vim at release 9.1.0 (Jan 2024)

      codeberg.org/NerdNextDoor/evi

      maybe we can get a group of people behind this??

      Fuck AI.

        [?]nixCraft 🐧 » 🌐
        @nixCraft@mastodon.social

        Sharing for lulz 🤣

        In this meme we see an elderly veteran in a dress uniform looking emotional and on the verge of tears, with the text that reads: "Me, having fought in the Vim–Emacs wars, seeing juniors vibe-code in Cursor”.

        Alt...In this meme we see an elderly veteran in a dress uniform looking emotional and on the verge of tears, with the text that reads: "Me, having fought in the Vim–Emacs wars, seeing juniors vibe-code in Cursor”.

          [?]MANCHUCK » 🌐
          @manchuck@phpc.social

          Well, little dude snuck into my office. He was bashing on my keyboard and managed to quit . I guess the whole infinite monkeys theory applies. 😀

            [?]JdeBP » 🌐
            @JdeBP@mastodonapp.uk

            @MGAceman

            I've been hit a couple of times by Control+Q and Control+W. The latter is habitual for either switching windows in VIM or erasing the last word in a terminal session.

              [?]R.L. Dane :Debian: :FreeBSD: :OpenBSD: :NetBSD:🍵 :MiraLovesYou: [he/him/my good fellow] » 🌐
              @rl_dane@polymaths.social

              C'mon #vim folk, REPRESENT!!

              @hyde

              #vi #nvi #neovim #nvim

                [?]R.L. Dane :Debian: :FreeBSD: :OpenBSD: :NetBSD:🍵 :MiraLovesYou: [he/him/my good fellow] » 🌐
                @rl_dane@polymaths.social

                Couldn't seem to get #VimClassic to compile on #FreeBSD.

                But then I realized the only thing I used it for is sncli, because it does something funny with the terminal when it hands it off to nvi, such that the cursor becomes invisible. But then, it's just a !reset to fix it, so I might as well just stick with nvi. ;)

                #vi #vim #nvi #TextEditors #PlainText

                  [?]JdeBP » 🌐
                  @JdeBP@mastodonapp.uk

                  @rl_dane

                  Fun fact: The :x command was added to ex/vi in 1980 because :wq did too much. Horton copied the name from hed.

                  github.com/dspinellis/unix-his

                  @rettichschnidi

                    [?]R.L. Dane :Debian: :FreeBSD: :OpenBSD: :NetBSD:🍵 :MiraLovesYou: [he/him/my good fellow] » 🌐
                    @rl_dane@polymaths.social

                    Dear #vim, darlin',

                    If you're gonna read my \.exrc, do me the kindness about not complaining about valid ex/#vi options! XD

                    rld@Intrepid:~$ vim
                    Error detected while processing /home/rld/.exrc:
                    line    4:
                    E518: Unknown option: iclower
                    
                    Press ENTER or type command to continue
                    

                    (I know, I know, just use a .vimrc. I'm gonna. ;)

                    (Also, just FYI, I haven't reverted to vim. I use vi and ed most of the time, and jump into vim for a very few use cases, which escape recollection at just this moment 😆)

                      [?]R.L. Dane :Debian: :FreeBSD: :OpenBSD: :NetBSD:🍵 :MiraLovesYou: [he/him/my good fellow] » 🌐
                      @rl_dane@polymaths.social

                      @rettichschnidi @adi

                      I was very fond of :up[date], which saves only if changes were made, but that's #vim (and descendants)-only, not #vi.

                      I'll see if my muscle memory allows me to rewrite ":q; ok then, :wq" as ":x" instead. 😄
                      (I'm a creature of habit ;)

                        [?]R.L. Dane :Debian: :FreeBSD: :OpenBSD: :NetBSD:🍵 :MiraLovesYou: [he/him/my good fellow] » 🌐
                        @rl_dane@polymaths.social

                        New #blog #post: Vim Carnival Entry: "The Motion that Changed Everything."

                        https://rldane.space/vim-carnival-entry-the-motion-that-changed-everything.html

                        1224 words

                        cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn

                        (I will happily add/remove you from the chorus upon request! :)

                        Thanks to @hyde for the blog concept, and immediate apologies if you get trapped in a #hellthread! 😄

                        #rlDaneWriting #blost #vi #vim #nvi #editor #VimCarnival #TheMotionThatChangedEverything #modal #ADHD

                          [?]Artyom Bologov [t?he(y|m)?, on(e)] » 🌐
                          @aartaka@merveilles.town

                          So I was writing this ed(1) wrapper editor. To have fancier search and custom commands, all with a nice immediate Web GUI.

                          And then I realized nvi(1) exists.

                          @ed1conf

                            [?]R.L. Dane :Debian: :FreeBSD: :OpenBSD: :NetBSD:🍵 :MiraLovesYou: [he/him/my good fellow] » 🌐
                            @rl_dane@polymaths.social

                            Trying out #nvi-1.81.6 on #Debian as my primary editor on my work box for a bit.

                            At first, I was sad that I could no longer

                            some_command |vi
                            

                            like you can with (neo)?vim, but then I realized you could just as easily

                            vi <(some_command)
                            

                            Hmmm, the lack of line selection mode is a bummer. This might have more pain points than I was anticipating. XD

                            Maybe I should try #vim-tiny?

                              [?]R.L. Dane :Debian: :FreeBSD: :OpenBSD: :NetBSD:🍵 :MiraLovesYou: [he/him/my good fellow] » 🌐
                              @rl_dane@polymaths.social

                              #vi experts (and #vim / #nvim #NeoVim ),

                              What's the difference between the 0 command and the | command?

                              Is it just that | can take a numeric argument?

                                [?]Thorsten Zöller » 🌐
                                @thorstenzoeller@exquisite.social

                                If you are seriously thinking about learning / , do yourself a favor and proceed as follows:

                                1. Grok ed(1).
                                2. Grok vi(1).
                                3. Ask yourself whether you really need anything ed(1) and vi(1) don't provide.

                                If your answer to step 3 is "yes", go ahead. But first, do steps 1 and 2.

                                Here is how to do step 1: Read the man page (it's rather short), read "Ed Mastery" by @mwl (those two steps are interchangeable and even parallelizable), then use it consistently.

                                Here is how to do step 2: Read the man page (it's rather short as well, though not as short as ed's), then use it consistently.

                                Also, have a look at stackoverflow.com/a/1220118.

                                  JdeBP boosted

                                  [?]JdeBP » 🌐
                                  @JdeBP@tty0.social

                                  #netbsd boosted

                                  [?]JdeBP » 🌐
                                  @JdeBP@tty0.social

                                  @jpmens

                                  I recently wrote jdebp.info/FGA/original-vi.htm and was thinking of doing something like this, to augment it; because Sven Guckes's list (guckes.net/vi/clones.html) is definitely dated and incomplete, nowadays.

                                  It does not have (for obvious reasons). Most lists of clones miss that there are several forks of Bostic , not least the two forks that are in and base. Similarly, has forked nvi2.

                                  @lpar

                                    [?]R.L. Dane :Debian: :FreeBSD: :OpenBSD: :NetBSD:🍵 :MiraLovesYou: [he/him/my good fellow] » 🌐
                                    @rl_dane@polymaths.social

                                    SOLUTION: @gumnos came up with the idea of piggy-backing :nohl onto control-l for refresh:

                                    nmap <C-L> :nohl<CR><C-L
                                    imap <C-L> <Esc>:nohl<CR><C-L>a
                                    

                                    Hey #vim wizards,

                                    The number one reason I don't use search more freely when editing is that all the highlights triggers my #CDO a little bit, and :nohl is a little clumsy to type in a hurry.

                                    I wanted to map :nohl to an easy-to-press keybind, like ctrl-/, but I can't seem to get it to work.

                                    Any ideas?

                                    " map Ctrl-/ to :nohl
                                    nmap <c-Slash> :nohl<CR>
                                    imap <c-Slash> <Esc>:nohl<CR>a
                                    

                                    #vi #vim #nvi #nvim #VimWizards #AskFedi #HiveMind

                                      [?]SWAT » 🌐
                                      @swat@fosstodon.org

                                      Does anyone know of a good method (may include software) to create ? This may include digital (on screen) and printed options.

                                      Background: I am using a and am using it more and more. In a keyboard centric workflow, I tend to forget all available shortcuts. Software I am using: with with (actually and neomutt

                                        /home/rqm boosted

                                        [?]kazé » 🌐
                                        @fabi1cazenave@mastodon.social

                                        Stolen from the nerdiscord.

                                        Screenshot on a DC anime.
— Superman, holding a mug of hot coffee: “so, you aren’t using AI”
— Batman replies: “I’m not even using a mouse”

                                        Alt...Screenshot on a DC anime. — Superman, holding a mug of hot coffee: “so, you aren’t using AI” — Batman replies: “I’m not even using a mouse”