this post was submitted on 30 Sep 2024
915 points (94.3% liked)

linuxmemes

24370 readers
1 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    915
    Me giving advice about text editors (lemmy.world)
    submitted 7 months ago by renzev@lemmy.world to c/linuxmemes@lemmy.world
    186 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] ShrimpCurler@lemmy.dbzer0.com 9 points 7 months ago (1 children)

    Sometimes it's not so easy to fire up a GUI, like when you ssh into another machine.

    [–] woelkchen@lemmy.world 1 points 7 months ago (1 children)

    Sometimes it’s not so easy to fire up a GUI, like when you ssh into another machine.

    CLI text editors have their specific use cases. For all other cases GUI ones (Kate, VSCode,...) exist.

    [–] nickwitha_k@lemmy.sdf.org 2 points 7 months ago

    CLI text editors have their specific use cases.

    Couldn't agree more. My use cases tend to be:

    • text editor
    • note taking
    • IDE
    • config editor
    • log viewer
    • adhoc data prep
    • json viewer

    EMACS users sometimes add web browser and email client, among other things but, that's a bit further than I go. The perf for either of the main two blows nearly any GUI editor out of the water and being able to pipe stdout/stderr to them is just the wonderful cherry on top.