w.i.p. Status PS1

3600 entries. Added new features, information and fixed errors.

Will be online when all ps1 entries are updated. 5100 to go.

#ps1 #psx #retrogame #playstation #manuals #hires #covers #adverts

We’ve refreshed the INSYDIUM Fused documentation from the ground up; now fully searchable and easier to navigate.

Every object also includes a “?” help button, linking you straight to its dedicated docs page.

Explore here: docs.insydium.ltd

#INSYDIUMFused #Documentation #Help #Manuals

Software manual for old Trimble 5600 I’m looking for a program manual for the Trimble 5602-03 or geodimeter 600. I did have one years ago but unfortunately it went away with the 600. Seams like each time I use it my memory is f...

Software manual for old Trimble 5600 #Surveying #Geospatial #Trimble #Manuals #SurveyEquipment

Notes on clarifying man pages Notes on clarifying man pages

💯!

“Notes On Clarifying Man Pages”, Julia Evans (jvns.ca/blog/2026/02...).

On HN: news.ycombinator.com/item?id=4706...

On Lobsters: lobste.rs/s/zpifkh/not...

#Unix #Linux #Manuals #ManPages #Documentation #Learning

Notes on clarifying man pages Hello! After spending some time working on the Git man pages last year, I’ve been thinking a little more about what makes a good man page. I’ve spent a lot of time writing cheat sheets for tools (tcpdump, git, dig, etc) which have a man page as their primary documentation. This is because I often find the man pages hard to navigate to get the information I want. Lately I’ve wondering – could the man page _itself_ have an amazing cheat sheet in it? What might make a man page easier to use? I’m still very early in thinking about this but I wanted to write down some quick notes. I asked some people on Mastodon for their favourite man pages, and here are some examples of interesting things I saw on those man pages. ### an OPTIONS SUMMARY If you’ve read a lot of man pages you’ve probably seen something like this in the `SYNOPSIS`: once you’re listing almost the entire alphabet, it’s hard ls [-@ABCFGHILOPRSTUWabcdefghiklmnopqrstuvwxy1%,] grep [-abcdDEFGHhIiJLlMmnOopqRSsUVvwXxZz] The rsync man page has a solution I’ve never seen before: it keeps its SYNOPSIS very terse, like this: Local: rsync [OPTION...] SRC... [DEST] and then has an “OPTIONS SUMMARY” section with a 1-line summary of each option, like this: --verbose, -v increase verbosity --info=FLAGS fine-grained informational verbosity --debug=FLAGS fine-grained debug verbosity --stderr=e|a|c change stderr output mode (default: errors) --quiet, -q suppress non-error messages --no-motd suppress daemon-mode MOTD Then later there’s the usual OPTIONS section with a full description of each option. ### an OPTIONS section organized by category The strace man page organizes its options by category (like “General”, “Startup”, “Tracing”, and “Filtering”, “Output Format”) instead of alphabetically. As an experiment I tried to take the `grep` man page and make an “OPTIONS SUMMARY” section grouped by category, you can see the results here. I’m not sure what I think of the results but it was a fun exercise. When I was writing that I was thinking about how I can never remember the name of the `-l` grep option. It always takes me what feels like forever to find it in the man page and I was trying to think of what structure would make it easier for me to find. Maybe categories? ### a cheat sheet A couple of people pointed me to the suite of Perl man pages (`perlfunc`, `perlre`, etc), and one thing I noticed was man perlcheat, which has cheat sheet sections like this: SYNTAX foreach (LIST) { } for (a;b;c) { } while (e) { } until (e) { } if (e) { } elsif (e) { } else { } unless (e) { } elsif (e) { } else { } given (e) { when (e) {} default {} } I think this is so cool and it makes me wonder if there are other ways to write condensed ASCII 80-character-wide cheat sheets for use in man pages. ### examples are very popular A common comment was something to the effect of “I like any man page that has examples”. Someone mentioned the OpenBSD man pages, and the openbsd tail man page has examples of the exact 2 ways I use tail at the end. I think I’ve most often seen the EXAMPLES section at the end of the man page, but some man pages (like the rsync man page from earlier) start with the examples. When I was working on the git-add and git rebase man pages I put a short example at the beginning. ### a table of contents, and links between sections This isn’t a property of the man page itself, but one issue with man pages in the terminal is it’s hard to know what sections the man page has. When working on the Git man pages, one thing Marie and I did was to add a table of contents to the sidebar of the HTML versions of the man pages hosted on the Git site. I’d also like to add more hyperlinks to the HTML versions of the Git man pages at some point, so that you can click on “INCOMPATIBLE OPTIONS” to get to that section. It’s very easy to add links like this in the Git project since Git’s man pages are generated with AsciiDoc. I think adding a table of contents and adding internal hyperlinks is kind of a nice middle ground where we can make some improvements to the man page format (in the HTML version of the man page at least) without maintaining a totally different form of documentation. Though for this to work you do need to set up a toolchain like Git’s AsciiDoc system. It would be amazing if there were some kind of universal system to make it easy to look up a specific option in a man page (“what does -a do?”). The best trick I know is use the man pager to search for something like `^ *-a` but I never remember to do it and instead just end up going through every instance of `-a` in the man page until I find what I’m looking for. ### examples for every option The curl man page has examples for every option, and there’s also a table of contents on the HTML version so you can more easily jump to the option you’re interested in. For instance the example for `--cert` makes it easy to see that you likely also want to pass the `--key` option, like this: curl --cert certfile --key keyfile https://example.com The way they implement this is that there’s [one file for each option](https://github.com/curl/curl/blob/dc08922a61efe546b318daf964514ffbf41583 25/docs/cmdline-opts/append.md) and there’s an “Example” field in that file. ### formatting data in a table Quite a few people said that man ascii was their favourite man page, which looks like this: Oct Dec Hex Char ─────────────────────────────────────────── 000 0 00 NUL '\0' (null character) 001 1 01 SOH (start of heading) 002 2 02 STX (start of text) 003 3 03 ETX (end of text) 004 4 04 EOT (end of transmission) 005 5 05 ENQ (enquiry) 006 6 06 ACK (acknowledge) 007 7 07 BEL '\a' (bell) 010 8 08 BS '\b' (backspace) 011 9 09 HT '\t' (horizontal tab) 012 10 0A LF '\n' (new line) Obviously `man ascii` is an unusual man page but I think what’s cool about this man page (other than the fact that it’s always useful to have an ASCII reference) is it’s very easy to scan to find the information you need because of the table format. It makes me wonder if there are more opportunities to display information in a “table” in a man page to make it easier to scan. ### the GNU approach When I talk about man pages it often comes up that the GNU coreutils man pages (for example man tail) don’t have examples, unlike the OpenBSD man pages, which do have examples. I’m not going to get into this too much because it seems like a fairly political topic and I definitely can’t do it justice here, but here are some things I believe to be true: * The GNU project prefers to maintain documentation in “info” manuals instead of man pages. This page says “the man pages are no longer being maintained”. * There are 3 ways to read “info” manuals: their HTML version, in Emacs, or with a standalone `info` tool. I’ve heard from some Emacs users that they like the Emacs info browser. I don’t think I’ve ever talked to anyone who uses the standalone `info` tool. * The info manual entry for tail is linked at the bottom of the man page, and it does have examples * The FSF used to sell print books of the GNU software manuals (and maybe they still do sometimes?) After a certain level of complexity a man page gets really hard to navigate: while I’ve never used the coreutils info manual and probably won’t, I would almost certainly prefer to use the GNU Bash reference manual or the The GNU C Library Reference Manual via their HTML documentation rather than through a man page. ### a few more man-page-adjacent things Here are some tools I think are interesting: * The fish shell comes with a Python script to automatically generate tab completions from man pages * tldr.sh is a community maintained database of examples, for example you can run it as `tldr grep`. Lots of people have told me they find it useful. * the Dash Mac docs browser has a nice man page viewer in it. I still use the terminal man page viewer but I like that it includes a table of contents, it looks like this: ### it’s interesting to think about a constrained format Man pages are such a constrained format and it’s fun to think about what you can do with such limited formatting options. Even though I’m very into writing I’ve always had a bad habit of never reading documentation and so it’s a little bit hard for me to think about what I actually find useful in man pages, I’m not sure whether I think most of the things in this post would improve my experience or not. (Except for examples, I LOVE examples) So I’d be interested to hear about other man pages that you think are well designed and what you like about them, the comments section is here.

Notes on clarifying man pages

#man #documentation #manuals #linux #unix #via-fediverse

Origin | Interest | Match

Hand-Drawn Game Guides - Metroid: Presented by Hand-Drawn Game Guides Suit up. There are bounties to collect.

It fall to me to bring to Bluesky awareness of Phillip Summers, who makes incredible hand-drawn NES game manuals, most of which are FREE. Here’s a link to the one he made for Metroid: #Metroid #NES #manuals www.handdrawngameguides.com/free-guides/...

Behold the Prohibited Marios of Nintendo's internal illustration manual from boingboing rss feed

Behold the Prohibited Marios of Nintendo's internal illustration manual
boingboing.net/2026/01/08/behold-the-pr...
#Games #leaks #manuals #Nintendo #boingboing

User Manuals 1.000.000+ free PDF manuals from more than 10.000 brands. Search and view your manual for free or ask other product owners.

I just stumbled on;

https://www.manual.nz/

If you're looking for manuals for common consumer devices, it's one to try

#manuals #RightToRepair

Apple adds battery, replacement tools for the 14-inch MacBook Pro with M5 to its Self Service Repair Store lineup This could come in handy. On Tuesday, Apple acknowledged that it had added a 14-inch MacBook Pro with M5 battery replacement kit to its Self Service Repair Store, the company also introducing a manual...

Apple adds battery replacement tools for the 14-inch MacBook Pro with M5 to its Self Service Repair store lineup

www.powerpage.org/apple-adds-b...

#Apple #battery #repair #replacement #14inchMacBookPro #M5 #SelfServiceRepair #store #manuals #tools #parts #retail #DIY

Parts List for the Berger 100C. Would anyone Know where I could get a Manual? Greetings All, I'm Gordon, a general Home Owner out here in California. I have an Old Sears Craftsman Farm Level gotten from my late Father's estate. I realized that the base needed some cl...

Parts List for the Berger 100C. Would anyone Know where I could get a Manual? #HomeImprovement #DIYProjects #Manuals #HomeOwners #Tools

7x Items sold on Olx (regional): Part.1

Mini owners handbook & servicing guide

Apple Macintosh 512k classic user’s guide

Apple Macintosh Hypercard Basics retro manual (without floppy disk)

#olx #apple #macintosh #minibrand #itemsold #shopping #selling #books #book #manuals

#retrogaming
#cloudyelling
#manuals

ManualsLib - Makes it easy to find manuals online!

///ManualsLib///
Search for instruction manuals online. Over 9.5 million manuals indexed.
www.manualslib.com
Find more resources at www.libresites.org
#instruction_manuals #manuals #ManualsLib #library #practical #DIY

#literacy
What is need are also a series of udate to the usual literacy curriculum. New #manuals are needed and educational books that can open up, asses and unite futural and contemporary concerns and struggles. One such examples is rh Romanian initiative of a manual due to be published in Dec.

ORGAN WORKS

🎶 Music for organ (digital PDF scores)
#ORGAN

#music payhip.com/b/mIur4
___

#SacredMusic #Composer #ContemporaryMusic #ClassicalMusic #Sheetmusic #score #NewMusic #OrganMusic #ModernClassical #OrganWork #Recital #Organscore #Repertoire #Organist #Orgelmusik #Church #Pipe #PipeOrgan #Manuals

GNOME 49 migliora prestazioni, grafica e accessibilità GNOME 49 porta nuove app, controlli HDR, prestazioni migliorate e un'interfaccia più coerente e più pulita, disponibile con Fedora 43 e Ubuntu 25.10.

💡 Rilasciato GNOME 49: migliora prestazioni, grafica e accessibilità

gomoot.com/rilasciato-g...

#app #blog #gnome49 #hdr #linux #manuals #nautilus #news #papers #showtime #tech #tecnologia #web

A quick overiew about how I write instructions in org-mode On Reddit, someone asked how to write software documentation in org-mode, and I had a lot to say. Reddit, being Reddit, however, wouldn’t let me post my long comment. That’s fine, I don’t like spreading knowledge in silos anyway. Here’s what I said: Hi, my job involves writing technical documentation (instructions mostly), and I use org-mode for it all the time. I polished my process over the years, and it’s a loooong answer to a lot of stuff you probably didn’t ask, but I’ll try to break down the major parts. First, I use Denote to write all my documentation, one file per tool or procedure if possible. Denote allows me to auto-associate files with keywords (for example, instructions for macOS vs Windows) and also shows me when I wrote the file automatically (it’s in the file name), so I know how old the information is. In the org-mode file itself, I often add notes using `C-c !`, an inactive timestep, so if there’s an update to a part of the instructions, I know what happened when. Something I don’t use for work but in my own notes is Denote’s dynamic blocks (a block of code with dynamic links to other org files), which serve as an index to quickly view related notes. In the org-mode file, besides the Denote options, I add options in the meta part to get rid of TOC (table of contents) and display images inline: `#+STARTUP: inlineimages` and `#+OPTIONS: num:nil`. I often use annotated images, which I embed into the org file and attach to the headers (so the images are connected to the files). A couple of years ago, I decided to adopt and use the Microsoft Style Guide (look it up, see if it’s for you) mostly to keep consistent. I don’t like Microsoft, but they have some documentations that make sense, and my work environment is Windows-based, so they cover what I need. There are other style guides out there; whatever you find, stick with it. The style guide is what tells you what words should be in bold (UI elements and buttons) vs what gets italicized (things you want to emphasize) or why you should use “select” over “click” or “tap” (because it’s more generic and applies to more UIs). It’s up to you how crazy you want to get. I find that it helps immensely, and it’s already become an integral part of my writing. When I write in org, I often use comments (`#` followed by a space and the comment) as a reminder of what I still want to cover as ideas come to me under the paragraph I’m currently writing. For example, in this long post, I had a `# what about images?` under what I was writing until I got to it as a reminder. I don’t use headers right away, unless it’s something obvious from the start, like an Introduction explaining what a certain tool is (first header) and then the process to use it (second header). I prefer numbered lists and quick steps in my instructions; each line describes one action, unless it’s something simple. I use links often - and here’s another important tip: I have `(setq org-export-with-broken-links t)` in my settings because org-mode expects nice normal links, but Microsoft products don’t always have them, and org-mode won’t let me export with what it considers broken unless I turn it off. I validate links later, in the finished product (by the way, always use `target=blank` in your links so when someone selects a link, it doesn’t hijack their window but opens another window or a tab). I don’t use in-document links (anchor links, forget what they’re called) because these don’t always work well. It’s better to tell your users something like “for uninstall instructions, see **header name** below,” and let them go there. Anchor links are confusing and can break when you export. When I’m done with my lists, I see if the sections make sense. I sometimes break into sub-sections, but if I go beyond 2nd level headers, I need to consider if I should expand into another article because it tells me the instructions are getting too complex. I got to expand a bit more about Images. Using images is almost always better, as long as they are clear and use consistent annotations (write your own style guide). I prefer arrows over circles because I find they draw the eye better, and I like using callouts with text (like in speech bubbles in comics), pointing to what I’m talking about in the images. I try to use the same text from the instructions in the images. So if step 3 in the instructions says “select **submit** ,” I will use a bubble pointing to that button in the image, and it will say “select **submit** ” exactly the same way. There’s more to say about images, but this goes beyond org-mode, so I’ll stop here with this. When I export, I use pandoc . I don’t like to use Emacs HTML exporter. The reason for that is that pandoc comes with more options and the ability to have a “template” Word document that will automatically stylize your document with the right colors, font, font sizes, etc. You tweak it once in Word and it’s good forever. I don’t like to use html from org-mode because it comes with a lot of extra “fluff” you need to strip away (it’s possible, you need to find the options in the Emacs manual and specify, I just got lazy), and also everyone at my workplace uses Word or SharePoint, so it’s just easier. I love Pandoc, and I highly recommend looking into it if you’re writing a lot. I can keep going… There are spell checkers and grammar checkers (not the same thing), and Emacs doesn’t really have a good built-in grammar check, in my opinion. I blogged about Harper not too long ago, and it’s a good tool that can be integrated into Emacs (especially if you’re on a Mac), but if you’re writing for large audiences, you might need something better. There’s more to say about videos vs images, and depending on what system you store your articles in, it affects what you want to do there (or don’t want to do there), as in if it’s a wiki or a ticketing system or some other content management system. But it’s time to grab some dinner. If you have specific questions, feel free to ask. I love talking about these things if it’s not obvious!

#TAONAW - #Emacs and #orgmode: A quick overiew about how I write #instructions in org-mode
taonaw.com/2025/08/28/a-quick-overi...

#documentation #manuals #pandoc

Apple expands Self Service Repair program to Canada If you’re way up north and an iPhone user, you’re going to like this. Apple has officially expanded its Self Service Repair program to Canada, offers Canadian iPhone owners an expanded set of tools to...

Apple expands Self Service Repair program to Canada

www.powerpage.org/apple-expand...

#Apple #repair #expansion #business #products #repair #SelfServiceRepair #program #Canada #international #iPhone #iPad #Mac #tools #manuals #hardware #hardwarerepair

The Photoshop CS3/CS4 wow! book, 2010

#AdobePhotoshop #Computergraphics #photoshop #creative #book #bookcover #booktwt #Handbooks #manuals

Creative photoshop portrait techniques, 2006

#portrait #photoshop #creative #book #bookcover #AdobePhotoshop #Photography #Handbooks #manuals

#scribaland HEARTBREAK
A romantic separation hurts, really hurts! #scribaland1 #heartbreak #authorsbooks #authorsclub #authorsclubs #authorsgroup #authorsgroups #authorscommunity #authorscommunities #library #calligraphy #style #styles #design #digital #manual #manuals #create #creating #creator #ai

Typemill 2.18.0: Kixote Redesign and Page Permissions New in version 2.18.0: Work with a fully redesigned AI interface, hide restricted pages from navigation, and run Typemill without the admin interface.

🚀 Typemill 2.18.0 is out with a sleek, redesigned AI interface and powerful new features like hiding restricted pages from your navigation. Dive into the full update: typemill.net/news/typemil...

#AI #writing #publishing #cms #content #docs #manuals

Watch my video on Custom #Booklets & #Manuals for #PS4 & #PS5 games!

Watch, Share & Like:

youtube.com/shorts/38wKu...

Some sick rummage sale finds #books #manuals #machining

#videogames #manuals i don't know what else to use as a tag

#scribaland A WHALE IN A LIFE
Looking into the eye of a whale can change your life! Exploration of relationship between humans and whales! #scribaland1 #whale #life #galeries #calligraphy #style #styles #design #digital #manual #manuals #creatives #creativity #quotes #proverbs #tet #texts #art #word

#scribaland ELSEWHERE
Everybody dreams about it but not the same! The unknown location seems to be attractive but be aware of disenchantment! #scribaland1 #elsewhere #manuals #create #style #styles #design #digital #manual #creating #creator #creators #creation #creations #creative #creatives #haiku

🚀 #INPROCAP is joining #BSBF2026 in Maastricht!
We’ll present the final training materials and 3 Instruction #Manuals designed to help small and medium sized #enterprises access the #BigScience procurement ecosystem.
Let’s connect at the forum!
🔗 www.bsbf2026.org

Neue CD-Manuals 06/2025: Porsche, FU Berlin, Herkunftskennzeichen Deutschland, u.a. - Design Tagebuch Sechs neue Brand-Manuals/Portale wurden in der Corporate-Design-Manual-Sammlung im dt aufgenommen. Neu hinzugekommen sind unter anderem Designvorgaben der folgenden Marken und Unternehmen: Porsche, He...

#CorporateDesign #Styleguides #Brand #Branding #Manuals