• 17 Posts
  • 502 Comments
Joined 1 year ago
cake
Cake day: January 19th, 2025

help-circle

  • When someone proposes, implements or enforces a clearly sensible rule, and someone else brings weird corner case scenarios up, always ask yourself if there’s a conflict of interests.

    I can’t tell if I started doing this more as disinformation became more prevalent over the recent years or it’s something I’ve always done; I don’t know where I would’ve picked it up from.

    Nevertheless, you’re spot on; it’s an incredibly good rule-of-thumb.

    (I just realized it might’ve been funny if I’d responded to this with a weird, corner-case scenario, instead; but it’s late and I can’t think of a good one for it)








  • (granted, you did mention that you could shoehorn this but) I don’t think a fragment of any sentence needs to have the sentence make sense if you remove the fragment; we jam fragments that are required to understand a sentence into all sorts of locations of sentences, all the time.

    The honest answer is that we don’t really have any hard rules about comma usage (as you point out, the sentence would work just as well without any commas), broadly, so people kind of just go vibes-based, most of the time.

    I feel like “did so with poor grammar” very obviously doesn’t feel like a tack on to a sentence (like, starting with a verb wouldn’t make sense) so I’m inclined to disagree but I’m anal about comma placement so maybe the average person would.





  • tomenzgg@midwest.socialtoComics@lemmy.blahaj.zoneMr Boopy
    link
    fedilink
    English
    arrow-up
    2
    ·
    18 days ago

    I mean, do you feel that it radically changes the sentence?

    While it specifies that especially the last line was general (which I agree), the sentence is still saying that Courtney’s entire comment was quite general while the very first sentence of her comment specifies it’s about this particular comic.

    The entire comment cannot be general when it contextualized its subject right from the first sentence.







  • So it’s possible I just never noticed the message noting minibuffer-next/previous-completion but those are pretty cool.

    But I think I was more thinking of tabbing in the opposite direction for minibuffer-complete; the situation I’m most often finding myself with such an abundance of options is when I’m exploring available functions and just looking; I rarely want to go one-by-one in such a scenario.

    …but what I just discovered is that functionality is already provided (I was confused when I saw that “backtab” was already assigned in minibuffer-local-completion-map); it just doesn’t seem to be there when auto-completing in Eval: (which just responds with “<backtab> is undefined”); which is how I’m most often looking at other available functions. That must be why I thought it never worked.

    Welp, I appreciate the info., regardless; I definitely learned a bit more than I knew before. And it’s good to know backtab will actually work in M-x, if I ever find I need it.


  • I tend to like it, too (though I can’t tell if that’s just because it’s what I first used and now I just expect it to work that way, now…).

    Do you know if there’s a way to go backwards through available options, though? I forget what shift+tab does but its not the inverse of tab and having to cycle all the way through to come back around on a particularly large list of options sure is tedious.

    I think that’s just about my only complaint with the default.