• 1 Post
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle



  • itsnotlupus@lemmy.worldtoLinux@lemmy.mlraw man files?
    link
    fedilink
    arrow-up
    27
    ·
    edit-2
    1 year ago

    You can list every man page installed on your system with man -k . , or just apropos .
    But that’s a lot of random junk. If you only want “executable programs or shell commands”, only grab man pages in section 1 with a apropos -s 1 .

    You can get the path of a man page by using whereis -m pwd (replace pwd with your page name.)

    You can convert a man page to html with man2html (may require apt get man2html or whatever equivalent applies to your distro.)
    That tool adds a couple of useless lines at the beginning of each file, so we’ll want to pipe its output into a | tail +3 to get rid of them.

    Combine all of these together in a questionable incantation, and you might end up with something like this:

    mkdir -p tmp ; cd tmp
    apropos -s 1 . | cut -d' ' -f1 | while read page; do whereis -m "$page" ; done | while read id path rest; do man2html "$path" | tail +3 > "${id::-1}.html"; done
    

    List every command in section 1, extract the id only. For each one, get a file path. For each id and file path (ignore the rest), convert to html and save it as a file named $id.html.

    It might take a little while to run, but then you could run firefox . or whatever and browse the resulting mess.

    Or keep tweaking all of this until it’s just right for you.












  • itsnotlupus@lemmy.worldtoaww@lemmy.worldDiscussion: AI Posts
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    1 year ago

    You can either go full bonzai and aggressively trim any little branch that pokes out of place to try to keep a meticulously maintained tree at all times, or you can just let the tree grows as it will, and if a branch becomes an obvious issue, then just cut the entire branch and graft it somewhere else.

    If I was a mod here, I would do the latter, maybe even setup an /c/AIAww or whatever in anticipation for what might come.
    That’s probably my laziness speaking.




  • I agree, but there’s a non-zero chance I don’t have a full picture of things yet, and maybe things aren’t that bad. Or won’t be that bad.

    On the surface, inconsistencies like this seem like they might encourage users to group themselves on a few massive servers that have a lot of local content guaranteed to be consistent rather than spreading themselves across many small instances (power law graph goes here.)

    But maybe not. I don’t know. Maybe the system naturally converges toward clusters of interests where each instance is primarily focused on a few things, and while the federation mechanism exists and is mostly useful, it is a secondary feature behind a primary use-case where folks preferentially engage with their local communities.

    Overall, I wonder how much of all this is colored by expectations we’ve developed while using Reddit.
    All this fediverse stuff is built on very different foundations than things like twitter or reddit, and while it’s easy to gloss over it because the UIs look superficially similar, they’ve made some fundamentally different trade-offs.

    But maybe the consistency stuff could get better over time too. Maybe there’ll be a smoother experience to better flag when and why things are inconsistent (“instance X hasn’t sent us activity updates since T”, “instance X has partially defederated from us”, etc.), and maybe even offer targeted palliative measures rather than a generic disclaimer.
    All this stuff is under fairly active development still, so there’s hope.


  • Welp, I’m new too, but I think this is more or less working as intended.

    The federation mechanism is a “best effort” thing, so there’s literally no guarantee that you’ll get the same view for the same thing loaded through two different instances.

    I started writing a userscript to “normalize” URLs so clicking on a link to kbin.social on a different instance would transform the link URL to keep you on your original instance, but with the distinct possibility of missing content because of it, I’m not sure it’s actually a good idea.

    The auto-refresh-and-btw-lemme-close-the-image-you-were-looking-at behavior isn’t happening on every instance, but it definitely happens on lemmy.world. Maybe this is an artifact of the websocket approach, and that’ll go away in 0.18? No idea.

    At this point, the usage pattern I’m leaning toward is to find good communities/magazines, subscribe to them, and stick to the “subscribed” view. The most consistent results will always be with subs that are local to the current instance, so if most of your subscriptions are on instance X, you probably don’t really want to have your account on instance Y.