Linux - partly off topic - searching for a new workflow lazarus / 21-General ---------------------------------------------------------------------- Nicole · 2025-06-12 13:50 Recently I changed from Windows to Linux. I miss very helpful tools. 1) One is called "Klebezettel NG" and old, outdated Windows software, which works like post-it. Double click at the tray icon shows a new one. At the moment I use in Linux xpad, which needs 2 clicks to show a new one and it does not stay at top of all windows by itself. "Klebezettel" (= sticking sheets) was that comfortable to have running several windows and just write on what you need to save. Do you have my "ideal" note-function for yourself in Linux? (if somebody likes to have Klebezettel for Windows, I can mail it. It may be not around any more. The nicest tool I found, and I searched a lot) 2) The next is Personal Backup. Written by an computer scientist who originally wrote it - to save his Delphi programming code. You do not want to save all the stuff crawling in our developer directories. This software allows to save exactly what we need. Unfortunately it is for windows only. What do you use? (at the moment I give deja double or similar a try) 3) How to get rid of the backup folder in Lazarus? There is never in it, what I have messed up. 4) In Windows I have had a system of saving my complete environment. This will not work in Linux any more. Do you have any depository either offline or without login every day? What I would need is to name versions alike "red car start worked", "green image display worked"... sometimes I need such a singe pas-file 6 months later. It must be EASY. e.g. github overwhelmed me and the double-login I hate. Thank you for sharing your everyday workflow. 5) and, this is that old "Greenshot". It allows to take screenshots, how boring. Additionally it allows to define a name by parameters of the file which is saved. e.g. "Monday Morning, the 12th of April" and takes the screenshot to any software you tell it to open. You can work on in your favourite graphic software and the background cares, the date of the first image is saved. 6) And I need a searching tool. At the moment I use Catfish and the Kitty seems to miss all. I had Agent Ransack, which is even better than Everything. But Windows only. ---------------------------------------------------------------------- Zvoni · 2025-06-12 14:20 @ 1) TomBoy-NG by our very own dbannon https://en.ubunlog.com/tomboy-ng-a-simple-note-taking-application-on- ubuntu/ @ 6) Search-Tool: https://forums.linuxmint.com/viewtopic.php?t=373643 For the life of me i can't remember the name of the tool i use on my Manjaro-Machines EDIT: Found it:SearchMonkey https://community.linuxmint.com/software/view/searchmonkey ---------------------------------------------------------------------- Martin_fr · 2025-06-12 14:57 3) Backups by Lazarus: Tools > Options ==> Environment > Backup There are 2 sections, both have "No backup file". I would recommend to keep some, just because compile will save files, and may overwrite something. 2) Backup for projects It may sound like overkill, but it is infinitely versatile: GIT. (try a few GUI clients to find one you like) When you create a new project, - create a local git repo for it "git init" - edit .git/info/exclude Code: Text  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i **/backup/*;[1-9]**/lib/****/*.lps**/*.o**/*.ppu**/*.or**/*.res- git add --all - git commit -m 'first version' You can commit every tiny change, even temporary => lots of rollback potential if things go south. (You can later learn to rebase and squash the micro commits into one big commit, or remove incorrect commits). You can add a "remote" in a different folder on the same disk, or on a different disk (e.g. usb stick) on your system. Then you can regularly push and voila you have a backup And you can get yourself an account with a githoster, and make online backups, if you want to. But you don't have to. You can also use that git to sync your laptop and your PC, or between different virtual machines. That works either via shared folders, or with git daemon - running your own git server. You can also keep "given up trial and error attempts" in some branch. So you still have them for reference... The possibilities are endless... You can even configure "external tools" in the IDE, to trigger git actions... I recently somewhere read about a tool (based on git) called gitbuttler, that is supposed to track your diskchanges, and keep them all. Supposedly you can go back and forth to any version you ever had on disk. I didn't try it, nor did I investigate it any further... ---------------------------------------------------------------------- paule32 · 2025-06-12 15:59 if it "old" Windows Software, you can let WINE a try. WINE = Wine Is Not a Emulator can run old Windows Software under Linux. To start your tour, let PlayOnLinux a try. This is a wrapper Software for WINE. It comes with portable Software Installer for a wide range of Software. As far as I know the Delphi Pedant on Linux was Kylix 3. And Kylix was driven by/under WINE ---------------------------------------------------------------------- Nicole · 2025-06-12 18:40 yes, this wine... I gave it a try already for a certain software. hm. Did not work. Not sure, if this was the fault of Wine or the software. This "Sticky Note" (Klebezettel) and the Personal Backup... I am quite sure, they will not work: The first slips into the windows right side task bar and shows on top of the windows. The windows windows. I would nearly bet, it cannot work. The Personal Backup uses the system of file-endings and user- directories of Windows. Is is married with Windows, I am afraid. I sent a mail to the developer. If it works, he will give me a hint. Maybe he even lets me have the source code. Then we can try it by ourselves. This backup is the best I ever have seen. If I cannot do it, somebody here can. ---------------------------------------------------------------------- paule32 · 2025-06-13 00:05 if you a Windows 95 Fan, there are a Project called ReactOS. It is a Free and Open Source Project which will aim to run on older Computer machienes and simulate a Windows Operating System. I followed it few years ago, so I can not tell you the current status of the Project. I only know, that the display driver was a Standard Driver and as such the Display is a little bit slow. But I was thinking to investigate some effort into the Project by makeing my own Display Driver with the support of VBE - also the extended graphics support (more colors, and more faster than Video Interrupt 12 - 16 Colors) - but that was only a mind experiment. The fact, that I am a Windows Fan tends me to investigate more Time in such a Project. Because new Windows Versions don't support my old Hardware - and I don't want to buy every year new. ---------------------------------------------------------------------- dbannon · 2025-06-13 01:14 Quote from: Zvoni on June 12, 2025, 04:20:20 pm@ 1) TomBoy-NG by our very own dbannon https://en.ubunlog.com/tomboy-ng-a-simple-note-taking-application-on- ubuntu/ https://github.com/tomboy-notes/tomboy-ng (Windows, Linux, Mac, and easy sync between them.) Davo ---------------------------------------------------------------------- CM630 · 2025-06-13 06:07 5) Flameshot Quote from: paule32 on June 13, 2025, 02:05:43 amif you a Windows 95 Fan, there are a Project called ReactOS. ... Sadly, it never reached even 1 % of the support it deserved. There is a new release from March, maybe it is not completely dead, but rather in the state of Schumacher. ---------------------------------------------------------------------- paule32 · 2025-06-13 06:44 it was not in my intention to make a flame war or a face palm. I am the opinion that each of us should use his/her own Operating System of choiche. Each of them and us have advantages and disadvantages. So, it makes no sense to propagate Linux, Windows, Mac or what ever. ---------------------------------------------------------------------- Thaddy · 2025-06-13 07:14 Quote from: CM630 on June 13, 2025, 08:07:51 amSadly, it never reached even 1 % of the support it deserved. There is a new release from March, maybe it is not completely dead, but rather in the state of Schumacher. Not exactly. The last few years they have been coöperating the Wine project and because of that made huge strides. In some countries it is even a state supported OS (everywhere ms can not be obtained legally). There are more reactOS users than you think. And there is a lot of sponsorship for it by well known companies. The fact that after 30 years or so there is not a formal stable release is just a joke. (maybe like fpc 4.0) After all, Windows itself is a moving target. And of course it runs Freepascal and Lazarus without flaws. The beauty of reactOS is that when some Windows software is NOT running on it, it is - bold statement with few exceptions - guaranteed that the program was written using undocumented stuff or with a completely new API. If you report that, it will get investigated and fixed. But since Wine code - which is very stable and well maintained - is now integrated that does not happen a lot anymore. I always have a couple of VM's that run it. And I know others do for the same reason. ---------------------------------------------------------------------- Warfley · 2025-06-13 09:07 QuoteDo you have my "ideal" note-function for yourself in Linux? (if somebody likes to have Klebezettel for Windows, I can mail it. It may be not around any more. The nicest tool I found, and I searched a lot)When it's about programming stuff I usually write TODOs into my code as comments, Lazarus has a TODOs functionality that scans your code after comments containing "TODO" and can neatly list them for you. QuoteThe next is Personal Backup. Written by an computer scientist who originally wrote it - to save his Delphi programming code. You do not want to save all the stuff crawling in our developer directories. This software allows to save exactly what we need. Unfortunately it is for windows only. What do you use? (at the moment I give deja double or similar a try)Git with a gitignore. It not just backups your code but also versions it. There are other tools like svn or mercurial but git is pretty much the most common one. Takes a bit to get into tho, and there are no good GUI tools so you better get comfortable with the command line QuoteHow to get rid of the backup folder in Lazarus? There is never in it, what I have messed up.You can deactivate backups in Lazarus, but if you are using git, you can clean your repository using "git clean -xdff" which will remove all files that are not tracked by git, so it will get rid of the backup folder, the compiled binaries and ppus, etc. QuoteIn Windows I have had a system of saving my complete environment. This will not work in Linux any more. Do you have any depository either offline or without login every day? What I would need is to name versions alike "red car start worked", "green image display worked"... sometimes I need such a singe pas-file 6 months later. It must be EASY. e.g. github overwhelmed me and the double-login I hate.Yeah, git: Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i git commit -a -m "implemented feature xyz" QuoteAnd I need a searching tool. At the moment I use Catfish and the Kitty seems to miss all. I had Agent Ransack, which is even better than Everything. But Windows only.Grep and find: Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i egrep -ir "Text to search for" srcWill search all files in src for the text "Text to search for", it's case insensitive and allows for regular expressions. If you want something from within Lazarus use Find in Files ---------------------------------------------------------------------- Martin_fr · 2025-06-13 09:43 About TODO: Some of my todo, are more like "someday that may need to be checked" notes. For those I use a combination of the "todo comment" and git. I make a todo-comment. Then I git commit it into a branch (the name usually starts with todo/ ). I then return to my main branch, and don't bother about that new branch. I can then periodically look at my branches starting with "todo/". Once in a blue moon, I rebase those branches to keep them in sync with other changes. The advantage is, that the note itself, is directly placed at the code to which it belongs. About SEARCHING git also allows you to search, when something was added or last changed. If you committed with a meaningful commit-message, then you that can help you finding out why something was implemented the way it is. See "git blame" As well as "git log -G filter" or "git log -S filter" (pickaxe) ---------------------------------------------------------------------- Nicole · 2025-06-13 14:44 this sounds great, desireable. My situation: There is my code and overwhelming new things and information there. On the other side there are a lot of things, which are called git. Gitlab, Github... I keep mixing them up. Logging in there I hate. It takes minutes, because it needs double check until it is working. When I am logged in there, - I lose orientation. There are so many branches and options and menus. Usually I click at one and am lost somewhere I never wanted to go and do not find back. To resume: Do you have a specific link to connect to a git? With no login every day? I think, 50 percent of my computer time is logging in somewhere. My Keepass has nearly 300 entries and many entries hold groups of passwords. ---------------------------------------------------------------------- Martin_fr · 2025-06-13 15:23 "git" is just a command line utility. "github"/"gitlab"/... are all just build around it. To install git, you do something like (depends on the version of linux) Code: Text  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i     sudo apt install gitBut before you do, just open a terminal, and type in "git" and see if it is there already. Many distros have some sort of GUI "software" installer. That may not offer "git", because it only does GUI, but it may offer "kgit" or "gitgui" (one of the frontends), and then it should install git as dependency). There are others: https://git-scm.com/downloads/guis Again: "git" is a local program. git needs no server. git needs no web-service. Look at my steps earlier to create a new git repo. Also check our wiki, it has a few steps. Mind you, git is extremely powerful. And while you can get the most basic steps git init git add git commit git log git checkout // or better: git switch and then later git branch git restore git stash git push  // git pull .... You will keep discovering and learning. And you will make error are couple of times, and it can get rough. 1) Don't force git, when you have files that you haven't committed yet. You can make git overwrite them. (And you probably don't want that) 2) If you end up lost, ask other first, then try your own. (or backup the entire folder: .git and all files) If you had a file committed, (so long as you don't play in the .git folder) then the file can be restored. Even if you can't see it, even if you think you deleted all references. git has an internal recycle bin, that keeps between 2 and 6 weeks of data. So files are there. Except: if you had never committed them. But then, the problem of overwriting files existed before git. The first couple of month, when I wasn't sure, I copied the entire folder (files and .git) before doing something that I hadn't done before. I know it sounds scary. But it is worth it. Really. Once you done the basics, you can set up git, to mirror into a 2nd folder. Then even if you delete the .git in one folder, you still have it in the other. ---------------------------------------------------------------------- CM630 · 2025-06-14 10:10 For windows there are  TortoiseSVN and TortoiseGit, I could not find something so comfortable for Linux. ---------------------------------------------------------------------- Warfley · 2025-06-14 10:26 TortoiseGit is not good. There are some git GUI tools which are not terrible, but they are all proprietary. If that is not an issue GitKraken is Ok-ish. But the problem is that git is designed through and through to be a command line tool, meaning it's not just a program with discrete operations, which can be easily integrated into a GUI, it's a set of commands that are intended to be combined and chained as somewhat of a language to interact with your repository. This is something that GUI tools are fundamentally not really capable of map intuitively. For example you work on a repository where someone made a force push. In that case you want to just fetch the data, inspect what was changed, was it just an amendmend to an existing commit, was it a reabse, was something deleted from the history, or a full restructuring of the branch, and in each of those cases you need to do something different. A GUI tool fundamentally cannot do that, it will usually see that fast forawrd was not possible and either ask you if you want to do a 3 Way Merge or a reset, the former can completely undo rebases, deletions or restructuring, the latter can completely nuke your whole work. This is simply not something that can be easily displayed in a message dialog with a discrete number of options. I had so many headaches already in projects where developers used GUI git tools and nuked branches, reverted changes etc. If you want to use git, learn to use git. There are no shortcuts and no fancy GUI software that makes it easy to use without getting to know the underlying system ---------------------------------------------------------------------- Thaddy · 2025-06-14 10:37 I recommend to start with Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i man giteverydayThis skips any super-advanced features and shows you the basic set of useful commands for beginners. There are many real world examples in this man. It is how I started with git after the move from svn, which I, admittedly, did not like very much at the time. No longer true: git is much better, well, flexible, except maybe for your own local repositories. There are many books about git, but you can simply start with the man. ---------------------------------------------------------------------- Thaddy · 2025-06-14 10:52 Quote from: Warfley on June 14, 2025, 12:26:57 pmTortoiseGit is not good. There are some git GUI tools which are not terrible, but they are all proprietary. Yes, agree with the "not good" part, not with the GUI part. Nope. Not all, not at all. https://git-scm.com/downloads/guis?os=linux Take your pick. I only use it from the command line, though. ---------------------------------------------------------------------- cdbc · 2025-06-14 11:01 Hi @Thaddy: man giteveryday is excellent advice =^ (<- thumbs up) For those of you who don't feel familiar with man-pages, attached is a text-file representation of those pages... Regards Benny ---------------------------------------------------------------------- Thaddy · 2025-06-14 11:31 @cdbc As suggested on the development page, for FreePascal you need just a one time git clone and subsequently a recurring git pull every week or so. I only do a rebase if Warfley has anything interesting and I have to apply a patch to test.. ---------------------------------------------------------------------- cdbc · 2025-06-14 12:06 Hi Thaddy Same as I do, mind you I only pull when I feel like it, not on a weekly basis, 'cause stability is more important to me than all the new shiny gizmos, that I don't have time to figure out anyway... (I'm building a new terrasse/deck for  the mrs. - pheewww) Regards Benny ---------------------------------------------------------------------- Martin_fr · 2025-06-14 12:45 Quote from: Warfley on June 14, 2025, 12:26:57 pmTortoiseGit is not good. That depends... It does make some alternation to how some git features a wrapped, it still shows that it comes from svn. That will affect people who make use of the index, and add stuff, but commit much later (in the added form, ignoring the worktree) It also doesn't expose all features. But it gives a good base line to work with. And it is well integrated into the OS (for people who like to call it from the context menu of the windows explorer). Actually, if you don't access it via windows explore, then you are indeed probably left with very very little. One thing I was missing, but able to tweak via the registry was a custom argument to "git log" (viewing all branches, except a list of filtered out). QuoteFor example you work on a repository where someone made a force push. In that case you want to just fetch the data, inspect what was changed, was it just an amendmend to an existing commit, was it a reabse, was something deleted from the history, or a full restructuring of the branch, and in each of those cases you need to do something different. A GUI tool fundamentally cannot do that, it will usually see that fast forawrd was not possible and either ask you if you want to do a 3 Way Merge or a reset, the former can completely undo rebases, deletions or restructuring, the latter can completely nuke your whole work. This is simply not something that can be easily displayed in a message dialog with a discrete number of options. Well ok, with command line you can have a script, that contains your favourite (re-)actions. Though that difference between commandline and gui is not git specific. But otherwise if I do "git pull" or "git fetch" or "git remote update" from commandline, then it will also download, and then try either ff or rebase depending on my "git config", and if that doesn't work, it leaves me with my old state. So does the GUI (at least Tortoisegit on any repo I have used it with). So then on the command line, I also have to deal with the forced update. Exactly like on the GUI. And on the GUI I can also make other choices. Once I said "do nothing, leave me with the diverted branches", then I can perform any operation that git has. (Assuming the GUI has an implementation that provides complete access to all git commands) Besides: Quote the latter can completely nuke your whole work.No, it can and does not. Well, that is unless you mean: - Not yet committed changes in the worktree  (or index: added but not committed). - You keep ignoring that something went wrong, for weeks until it then eventually actually gets "nuked" - You do a "prune" (gc) to confirm that you want your accident to be unrecoverable. By default, your local branch (which is what you most likely stand to "reset" by accident) has a reflog => and that saves the old state for 6 weeks. (You can make that longer). So you have 6 weeks to restore your work, if you indeed made a bad decision and did something that "reset" your branch. Even if you don't have a reflog, git does not remove the "loose objects" for 2 weeks. So within those 2 weeks you can use "git fsck" to find those objects and restore them (that however is a lot of work... / so better go with the reflog). And to be clear, if someone isn't going to look at the result of their actions (and not noting something went wrong)... If they don't do that, not even when using a GUI that - if nothing else - does make it easy (easier) to look at a log and associated diffs)... Well, then that person most certainly would not check the result of what they did, if they had used command line. QuoteI had so many headaches already in projects where developers used GUI git tools and nuked branches, reverted changes etc. And people using the command line do never make mistakes? Well, in my experience they do. When something does not work as they want, they start using "-f" and override stuff. Calling "git reset" is easy enough. Creating a branch with force too. And with "git switch" all it takes is an uppercase -C, that can happen very easily, even by mistake instead of the lowercase -c And as for any statistical relevance between those errors, and GUI users: Are you sure they show the right cause vs effect relationship. If (assumed for arguments sake) GUI user make more mistakes, does that mean: - the GUI leads to mistakes - people who don't want to spend time to understand are more likely to use GUI ? Because the latter means, if they did not have a GUI, the still would do minimum investment to understand, and they would make the errors using command line too. QuoteIf you want to use git, learn to use git. Yes, of course. Learning and understanding it is important. But you can do that with a gui too. You just have to be willing to understand what you actually have the GUI do. But then on the command line, you have to also be willing to learn. ---------------------------------------------------------------------- Warfley · 2025-06-14 14:56 Quote from: Martin_fr on June 14, 2025, 02:45:23 pmWell ok, with command line you can have a script, that contains your favourite (re-)actions. Though that difference between commandline and gui is not git specific. But otherwise if I do "git pull" or "git fetch" or "git remote update" from commandline, then it will also download, and then try either ff or rebase depending on my "git config", and if that doesn't work, it leaves me with my old state. So does the GUI (at least Tortoisegit on any repo I have used it with). So then on the command line, I also have to deal with the forced update. Exactly like on the GUI.There are two kinds of GUIs for warpping command line tools. Those that just wrap the primitives, like the git gui that is shipped with git for windows, with those things you are completely right, there is not much of a difference. But these tools are either incomplete or hardly usable, because they need to encode all the options and combinations of the command line tool and replace the need of typing with an overwelmingly cluttered gui of dozens of checkboxes, buttons and co. Also there is absolutely no benefit for beginners as these GUIs have exactly the same complexity as the command line interface, just tend to be incomplete (because the commandline has so many options that not all will be included) The other kind of GUI application is like Tortoise Git or Git Kraken, which try to streamline git workflows into GUI processes. Here they make deliberate decisions on what command is executed when, which imposes massive restrictions on what the user can (easily) do and often get the user in some weird situations if anything does not happen as the designers of the GUI have forseen. Quote from: Martin_fr on June 14, 2025, 02:45:23 pmWell, that is unless you mean: - Not yet committed changes in the worktree  (or index: added but not committed). - You keep ignoring that something went wrong, for weeks until it then eventually actually gets "nuked" - You do a "prune" (gc) to confirm that you want your accident to be unrecoverable. Of course if you don't do a prune the commits might still be there. But I am talking explicitly about the situation where someone is so inexperienced with git that they don't know what a reset is and accidentally did a reset because when the GUI application encountered an error it had two buttons, 3 way merge and reset and they decided to click reset because they thought this will get it back to their previous state. Quote from: Martin_fr on June 14, 2025, 02:45:23 pmAnd people using the command line do never make mistakes? Well, in my experience they do. When something does not work as they want, they start using "-f" and override stuff. Calling "git reset" is easy enough. Creating a branch with force too. And with "git switch" all it takes is an uppercase -C, that can happen very easily, even by mistake instead of the lowercase -c And as for any statistical relevance between those errors, and GUI users: Are you sure they show the right cause vs effect relationship. If (assumed for arguments sake) GUI user make more mistakes, does that mean: - the GUI leads to mistakes - people who don't want to spend time to understand are more likely to use GUI ? Well it's much easier to accidentally click a button "reset" than it is to accidentally type in "git reset --hard origin/branchname". With a command line you must actively seek out what you are doing in order to type things up. In a GUI that just presents buttons to you you can just click. This is specifically a problem because most git GUI tools are sold under the premise that they make git easy and that you don't need to learn the complex command line tools. But thats the fallacy here, if you don't want to learn how git works internally, you will end up in situations as described above. And if you want to learn how git works, the best way is to use the command line where every command you write gives you immediate feedback, where when you mistype you get suggestions what you might wanted to type, and where the program gives very useful hints in every command. If you decide to use a GUI afterwards, thats fine, even though I would argue that if you know what you are doing the CLI will be always faster and more comfortable, but recommending beginners a GUI (especially if it has very specialized workflows) because they don't need to learn raw git that way is just a recipe for disaster ---------------------------------------------------------------------- Martin_fr · 2025-06-14 15:27 To summarise: It's not GUI in particular that will get you to make error that lead to loss (down the road). It's a subset of GUIs, that are badly designed. Tortoise has never ask me that particular question. So I never had that danger. Of course it has "reset" in the context menu. So if I am blindly looking for an option... Then I will pay the price. But to that I uphold, command line is not much difference. At least from what I observe. Few people in such a situation are studying the manpage (as they don't know which "git xyz" command they need the manpage for). Instead the most often taken course is stackoverflow (or similar), and that way it is fairly easy to get a "git reset ....". (I have seen cases exactly like that) I started on a mix of GUI and command line, and despite looking through manpages,  I did make mistakes in the first few month of learning (and a more than fair share of them from commandline). I don't recall all of them. But they ended in me having to backup, delete, and create a new repo with whatever files I had managed to save (and loss of history). So I can attest from my own experience, and from that of others whom I have helped => commandline does not prevent getting stuck. Not a bit. Getting stuck is part of the learning. I do agree so, certain more specialized task will require command line (or be easier on cmd line). I don't see any point in putting every last option behind a GUI. But, all the day by day stuff, can be wonderfully done via GUI. - A visual log, with the ability to click one of the changed files to see the diffs, rather than to have to type the name of the file on the cmd line. - A tool to add/commit, to allow inspection of the diffs, in the same "by click" manner. - A visual blame tool - even basic interactive rebase => to quickly select the branches involved. And arrange the picked commits (again being able to see diffs "by click") Sure a good shell can reduce the typing a lot. But it still leaves you with toggling between shells, if you hold the log in one shell, and use another to view diffs for some entry on the log... ---------------------------------------------------------------------- Warfley · 2025-06-14 16:55 Quote from: Martin_fr on June 14, 2025, 05:27:46 pmOf course it has "reset" in the context menu. So if I am blindly looking for an option... Then I will pay the price. But to that I uphold, command line is not much difference. At least from what I observe. Few people in such a situation are studying the manpage (as they don't know which "git xyz" command they need the manpage for). Instead the most often taken course is stackoverflow (or similar), and that way it is fairly easy to get a "git reset ....". (I have seen cases exactly like that) My main experience was leading a team where no one had experience with git except for me, and it was a really nice case study of the differnt UI tools. I had people use Tortoise Git, the Github git tool, GitKraken and some used the command line tool. And from my experience those that expressly wanted to learn how to use the command line tool and read up on that had the least problems and were most willing to learn. When the ones using the GUI fucked something up and I had to fix it, they didn't even bother trying to understand what I do because they felt like they won't be using the cli anyway so why bother checking what I am doing there. Again, if you want to learn git, you should learn all of the git commands and their options, and the best way for doing this is the command line. Quote from: Martin_fr on June 14, 2025, 05:27:46 pm- A tool to add/commit, to allow inspection of the diffs, in the same "by click" manner. Have you tried patch adding (git add -p)? This will show you each of the changes and let's you decide on a change by change basis if you want to stage, discard it or just ignore it. ---------------------------------------------------------------------- Martin_fr · 2025-06-14 17:49 Quote from: Warfley on June 14, 2025, 06:55:04 pm those that expressly wanted to learn how to use the command line tool and read up on that had the least problems and were most willing to learn. Ah, but that is what I meant by cause and effect. - The GUI did not cause people to make more errors. - It was chosen by people who were more error prone to begin with. I.e. people who wanted to short circuit the learning (leading to them making more errors) wanted to use the GUI. But, if people who would not proper read up, would have been given the command line, I would expect it likely they would have failed too. Trying to learn (and really understand) git from its manpages (or even some real tutorial), is much more time consuming than searching for a few "ready to use examples". Only the "ready to use examples" will likely get you to the same mistakes that were made using the GUI. If you take 2 people, who are equally willing to do the learning. And who both actually invest the time into learning, then I would not expect that the choice GUI vs Cmd-line had a huge impact. Well, yes. Some GUIs may have bad design, and mislead... But, even the command line git utility has bad design (less in terms of misleading, more in terms of memorize-ability), when it comes to naming of some of the commands. That is why some of the GIT team members started to replace parts of it (introducing "git switch"). Unfortunately, it's not perfect either, and the efforts into it have stalled over time... (apparently). ---------------------------------------------------------------------- Martin_fr · 2025-06-14 17:52 Just to say: git is often described as Swiss army knife. It is not. It is more like that weapon from 5th element (search youtube for "5th element red button". You need to learn it, or you get harmed. ---------------------------------------------------------------------- CM630 · 2025-06-14 20:38 There was CVS, then SVN, now another fashion - GIT... GIT has some benefits for ultaparanoids, but is it worth learning it ? Maybe something new and trendy will come up in September... ---------------------------------------------------------------------- Warfley · 2025-06-14 20:51 Quote from: CM630 on June 14, 2025, 10:38:42 pmThere was CVS, then SVN, now another fashion - GIT... GIT has some benefits for ultaparanoids, but is it worth learning it ? Maybe something new and trendy will come up in September... Git is around for 20 years now and is the industry standard for like 10-15 of those years. And there have been other (and in some ways definitely better) approaches liker Mercurial, but git is so well established by now, I do not think that it will be gone anytime soon. If it dies out it will be like SVN a process of years if not decades. So if you learn git today you'll be good for probably the next decade