BLAZE-LOG(1)

πŸ“¦
version 1.2.0 Β· 2 versions
, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble

πŸ’– BLAZE-LOG πŸ’–

okay bestie, welcome to the blaze-log page, straight out of the BlazeBlogger Documentation, section 1 of the manual. this is the girl who shows you your repo's whole diary. let's get into it πŸŽ€


✨ NAME ✨

blaze-log β€” she displays the BlazeBlogger repository log. that's it. that's her whole job and she ate πŸ’…


🌸 SYNOPSIS 🌸

blaze-log [-cqrsCV] [-b directory] [-n number]

blaze-log -h|-v

look at her. compact. iconic. no notes. ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

blaze-log displays the content of the BlazeBlogger repository log. like, the receipts of everything that ever happened in your repo. she's not judging, she's just reading them out loud 🫢


πŸ’… OPTIONS πŸ’…

  • -b directory, --blogdir directory β€” lets you say exactly which directory the BlazeBlogger repository lives in. don't give her one and she'll just assume the current working directory, no biggie.
  • -n number, --number number β€” lets you cap how many log entries get listed. you want number entries, you get number entries, periodt.
  • -s, --short β€” tells blaze-log to put each log entry on a single line. the lite mode. the snack-sized version πŸ“
  • -r, --reverse β€” tells blaze-log to list the log entries in reverse order. newest-to-oldest main character energy.
  • -c, --color β€” turns colored output ON. and when you supply it, it overrides the relevant configuration option. she said I decide the colors πŸ’…
  • -C, --no-color β€” turns colored output OFF. also overrides the relevant configuration option when supplied. mutual exclusivity who? just kidding, they fight, you pick one.
  • -q, --quiet β€” disables displaying of unnecessary messages. minimalism era 🌸
  • -V, --verbose β€” enables displaying of all messages. this is the default option, so she's already yapping, bestie.
  • -h, --help β€” displays usage information and exits. she's helpful like that πŸ’–
  • -v, --version β€” displays version information and exits. the "who even am i" flag.

πŸŽ€ FILES πŸŽ€

  • .blaze/log β€” a file containing the repository log. that's the one she's reading from, iykyk πŸ“–

🌈 EXAMPLE USAGE 🌈

list the whole repository history:

~]$ blaze-log
Date: Sun Jul 25 16:48:22 2010

    Edited the page with ID 5.

Date: Tue Jul  6 18:54:59 2010

    Edited the page with ID 5.

etc.

list the whole repository history in reverse order:

~]$ blaze-log -r
Date: Tue Feb 10 00:40:16 2009

    Created/recovered a BlazeBlogger repository.

Date: Tue Feb 10 01:06:44 2009

    Added the page with ID 1.

etc.

display the very first log entry on a single line:

~]$ blaze-log -rs -n 1
Tue Feb 10 00:40:16 2009 - Created/recovered a BlazeBlogger repository.

see that last one? reverse + short + one entry. literally the most efficient girl in the room πŸ‘‘


πŸ‘€ SEE ALSO πŸ‘€

blaze-init(1), blaze-config(1)

go read those too, they're her friends 🫢


πŸ’€ BUGS πŸ’€

to report a bug or to send a patch, please, add a new issue to the bug tracker at <http://code.google.com/p/blazeblogger/issues/>, or visit the discussion group at <http://groups.google.com/group/blazeblogger/>.

not me asking you to file an actual issue instead of vagueposting about it 😭 she wants the receipts.

Copyright (C) 2009-2011 Jaromir Hradilek

This program is free software; see the source for copying conditions. It is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

fr fr: free software, but no warranty, no cap. read that twice bestie 🫢

and that's the whole page, babes πŸ’– this was Version 1.2.0, dated 2019-10-07, from the BlazeBlogger crew β€” thanks for reading, now go check your log, slay βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from