• 0 Posts
  • 62 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • I don’t even now how anyone keeps track of them and finds the ones they want. And how can you possibly do that quicker than just going to the page afresh.

    Part of working on a project for me is assembling links to important pages. It may be days, weeks or months later that I want to come back and there are the links. And of course, anything generically or regularly useful is just a bookmark as you say.

    It really seems like people keep tabs open just to keep a list of useful pages. There are much easier and more effective ways to do that.


  • No, it’s a shell feature. Terminal emulators don’t even know what shell are running typically, and I haven’t heard of them adding shell features. That would require the terminal emulator knowing you’re using bash, knowing how to interrogate history etc…

    From man bash:

           yank-last-arg (M-., M-_)
                  Insert  the last argument to the previous command (the last word
                  of the previous history entry).  With a numeric argument, behave
                  exactly  like  yank-nth-arg.   Successive calls to yank-last-arg
                  move back through the history list, inserting the last word  (or
                  the  word  specified  by the argument to the first call) of each
                  line in turn.  Any numeric argument supplied to these successive
                  calls  determines  the direction to move through the history.  A
                  negative argument switches the  direction  through  the  history
                  (back or forward).  The history expansion facilities are used to
                  extract the last word, as if the "!$" history expansion had been
                  specified.
    



  • sping@lemmy.sdf.orgtoProgrammer Humor@lemmy.mlEDitor wars
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 month ago

    it always entertains me when a vim aficionado regurgitates the “just missing a good editor” joke, given that one of the editors Emacs offers is a pretty comprehensive clone of vim.

    (personally, I never had any problem with the default editor when I migrated to it from vi, though I was using a keyboard that already had ctrl next to a.)



  • Sorry it’s not a very direct answer but this is one of the many things that make Emacs such a comfortable environment once you’re used to it, which takes … a while.

    There is a man command and then of course it’s just more text displayed so you can search and narrow and highlight etc. in the same way you do with any other text. Plus of course there are a few trivial bonuses like links to other man pages being clickable.

    It’s all text and Emacs is a text manipulation framework (that naturally includes some editors).










  • I’ve worked in a few startups, and it always annoys me when people say they don’t have time to do it right. You don’t have time not to do it right - code structure and clarity is needed even as a solo dev, as you say, for future you. Barfing out code on the basis of “it works, so ship it” you’ll be tied up in your own spaghetti in a few months. Hence the traditional clean-sheet rewrite that comes along after 18-24 months that really brings progress to its knees.

    Ironically I just left the startup world for a larger more established company and the code is some of the worst I’ve seen in a decade. e.g. core interface definitions without even have a sentence explaining the purpose of required functions. Think “you’re required to provide a function called “performControl()”, but to work out its responsibilities you’re going to have to reverse-engineer the codebase”. Worst of all this unprofessional crap is part of that ground-up 2nd attempt rewrite.



  • These are arguments talking past each other. Sure 1 useful comment and 9 redundant ones can be better than zero, but comments are not reliable and often get overlooked in code changes and become misleading, sometimes critically misleading. So often the choice is between not enough comments versus many comments that you cannot trust and will sometimes tell you flat-out lies and overall just add to the difficulty of reading the code.

    There’s no virtue in the number of comments, high or low. The virtue is in the presence of quality comments. If we try to argue about how many there should be we can talk past each other forever.


  • My guess at the stance is I’d imagine it’s that switching away from snaps is switching away from Ubuntu’s support and security monitoring and updates to some less known/reliable/diligent third party?

    Popey (Alan Pope) used to work for Canonical / Ubuntu, so he’s presumably not inclined to jump on the bandwagon of Canonical/Ubuntu/snap hate since he knows a lot of Canonical and Ubuntu people and their motivations and work. Not that there aren’t good reasons to criticize snap or other Canonical decisions, but it’s also plain that a lot of people just join a hate bandwagon and don’t even know what about it they object to. There is masses of wrong-headed criticism of Canonical out there e.g. I’ve frequently seen people criticize creating Upstart, saying Canonical should have used systemd, or bzr vs git! Presumably these people were annoyed at Canonical for not inventing a time machine.