• Oriel Jutty :hhHHHAAAH:@infosec.exchange
    link
    fedilink
    arrow-up
    17
    arrow-down
    2
    ·
    edit-2
    2 days ago

    POV: You open vim for the first time.

    ![Screenshot of vim start screen. The instruction to exit vim is highlighted in red. It reads:

    VIM - Vi IMproved

    version 9.1.697 by Bram Moolenaar et al. Modified by team+vim@tracker.debian.org Vim is open source and freely distributable

    Help poor children in Uganda! type :help iccf<Enter> for information

    type :q<Enter> to exit type :help<Enter> or <F1> for on-line help type :help version9<Enter> for version info](https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/654/520/326/340/201/original/3df1e7f1fb9b8619.png)

    • pinball_wizard@lemmy.zip
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      9 hours ago

      Fair, but there’s a worse experience possible.

      For a time, many people’s first encounter with vi was when it auto-opened a temporary editor to ask them to submit a commit message for the git command they just ran.

      This experience skips the vi “welcome” screen, because a file is open.

      As a bonus challenge, git did not inform the user what editor is in use, and the user had no particular reason to even expect an editor to appear, based on what they were just doing.

      None of this was the fault of vi, really. But it was a terrible introduction.

      It got better when various operating systems changed their default command line editor to nano, and git added some helpful adjustments - “if certain settings are not configured, assume a new user and show verbose welcome messages”.

      • Simon 𐕣he 🪨 Johnson@lemmy.ml
        link
        fedilink
        arrow-up
        1
        arrow-down
        3
        ·
        edit-2
        1 day ago

        The image shows the last state of a terminal emulator of person without command line or git knowledge. The person attempted to run git commit and is now blaming the result of a specific configuration on their system that launches a vi derivative on the vi derivative itself. This image is expected to convince the viewer that the vi derrivative is to blame.