LOG(nged)

used to control logging

πŸ“… published 7.44.0, from nixpkgs unstable

πŸŽ€ log πŸ’… (the nged manual page) πŸŽ€

okay so bestie, welcome to the log page from the nged corner of the BRL-CAD manuals β€” this one's short, sweet, and lowkey iconic ✨


🌸 NAME 🌸

log β€” the command that controls logging 🫢


πŸ’– SYNOPSIS πŸ’–

log get|start|stop

πŸ¦‹ DESCRIPTION πŸ¦‹

So the log command is literally the remote control for capturing bu_log output β€” that's BRL-CAD's internal logging system, fyi β€” and it drops all of it into an internal buffer that's attached to your current session πŸ’… no cap.

The three subcommands are, in no particular order except the order they're in:

  • start β€” installs a hook into the bu_log system that intercepts all the subsequent log messages and appends them to an internal buffer (that's ged_log for the note-takers πŸ“). The way that after you call log start, log messages just accumulate silently in the buffer instead of being printed immediately? obsessed. 🀫
  • stop β€” removes the logging hook and restores normal bu_log output behavior. Messages are no longer captured to the buffer. bye bestie πŸ‘‹
  • get β€” retrieves and clears the contents of the accumulated log buffer, handing you back all the captured messages since the last log start. Heads up though: the buffer is emptied after this call πŸ™ˆ so grab it while you can.

✨ EXAMPLES ✨

🌈 Example 1. Capture and retrieve log output 🌈

mged> log start
mged> draw some_object.r
mged> log stop
mged> log get

What's happening here, step by step, because iykyk:

  1. starts capturing log output 🎬
  2. draws an object (which may produce internal log messages β€” sneaky little things) 🎨
  3. stops capturing βœ‹
  4. then retrieves and prints all the log messages that were generated during the draw operation πŸ’Œ

slay. periodt. πŸ‘‘


πŸ‘‘ AUTHOR πŸ‘‘

BRL-CAD Team 🫢 (genuinely the main characters of this whole thing)


πŸ“ BUG REPORTS πŸ“

If you find a bug or a problem, reports should be submitted via electronic mail to devs@brlcad.org πŸ“§ β€” they literally want to hear from you, so don't be shy.


fr fr though: get empties the buffer after it runs. that's not a vibe check you can redo, so if you need those messages twice, save them. πŸ’€

and that's the whole page, bestie πŸ§šπŸ’œ this little gem lives in the BRL-CAD user commands collection, filed under the nged manual as LOG(nged) β€” catch you in the next one, mwah πŸ’‹πŸŽ€

πŸ“¦ where this page comes from