Post #703141
2026-03-18 17:59 UTC
Replies (13)
-
@george@a2mi.social 2026-03-18 18:30
@onorio I need check boxes, not radio buttons, and IDE as an option
-
@nicd@masto.ahlcode.fi 2026-03-18 18:39
@onorio Command line for other things, git-gui for making commits unless they're dead simple.
-
@NuclearSquid@piaille.fr 2026-03-18 20:02
@onorio Voting « Command Line » but it’s actually TUI. Tools like Tig (and later Serie) and especially LazyGit do basically 95% of my git workflow (if you exclude the git status I have with my ls command)
-
@thedaemon@snac.9front.club 2026-03-18 20:08
There is a GUI?
-
@nono@pleroma.oook.fr 2026-03-18 22:18
@onorio Both. Wait... Emacs does qualify as a GUI, right?
-
@butterscotch@aus.social 2026-03-18 22:22
@onorio in the IDE of choice
-
@patrick_h_lauke@mastodon.social 2026-03-18 22:58
@onorio to clarify: i use the same 5 or 6 commands i've memorised for CLI ... and anything more complex I just do a search for :)
-
@bohwaz@mamot.fr 2026-03-18 23:39
@onorio With great difficulty. The command names are absurd.
-
@TeaDrivenDev@metalhead.club 2026-03-19 00:55
@onorio I voted "command line", but it's a mix of both. I usually commit from inside the IDE and use a UI for information dense things like checking history, but any other day-to-day usage is on the command line.
-
@lamecarlate@pouet.it 2026-03-19 06:55
@onorio … Both? By force of habit, some tasks I do with a GUI (git-cola, essentially for git add, because it lets me easily see the diffs of each file), some with the CLI :D
-
@pierstoval@mastodon.social 2026-03-19 09:06
@onorio the only GUI I use is the conflict resolution tool from my IDE
-
@brab@framapiaf.org 2026-03-19 12:34
@onorio magit in emacs, so I chose GUI
-
@tshirtman@mas.to 2026-03-20 21:53
@onorio cli, and vim plugin (fugitive, so more TUI). But more and more… through an agent, sorry, not because i can't do otherwise, but because it make sense as part of the loop.