File Manager

X7ROOT File Manager

Current Path: /opt/alt/ruby18/share/ri/1.8/system/Logger

opt / alt / ruby18 / share / ri / 1.8 / system / Logger /

ðŸ“„ %3c%3c-i.yaml(306 B)
ðŸ“ ..
ðŸ“ Application
ðŸ“ Error
ðŸ“ Formatter
ðŸ“ LogDevice
ðŸ“ Severity
ðŸ“ ShiftingError
ðŸ“„ add-i.yaml(2.48 KB)
ðŸ“„ cdesc-Logger.yaml(10.09 KB)
ðŸ“„ close-i.yaml(226 B)
ðŸ“„ datetime_format%3d-i.yaml(300 B)
ðŸ“„ datetime_format-i.yaml(184 B)
ðŸ“„ debug%3f-i.yaml(307 B)
ðŸ“„ debug-i.yaml(322 B)
ðŸ“„ error%3f-i.yaml(307 B)
ðŸ“„ error-i.yaml(323 B)
ðŸ“„ fatal%3f-i.yaml(307 B)
ðŸ“„ fatal-i.yaml(322 B)
ðŸ“„ format_message-i.yaml(216 B)
ðŸ“„ format_severity-i.yaml(193 B)
ðŸ“„ info%3f-i.yaml(304 B)
ðŸ“„ info-i.yaml(1.06 KB)
ðŸ“„ log-i.yaml(260 B)
ðŸ“„ new-c.yaml(1.11 KB)
ðŸ“„ unknown-i.yaml(383 B)
ðŸ“„ warn%3f-i.yaml(304 B)
ðŸ“„ warn-i.yaml(319 B)

Editing: info-i.yaml

--- !ruby/object:RI::MethodDescription 
aliases: []

block_params: 
comment: 
- !ruby/struct:SM::Flow::P 
  body: Log an <tt>INFO</tt> message.
- !ruby/struct:SM::Flow::P 
  body: The message can come either from the <tt>progname</tt> argument or the <tt>block</tt>. If both are provided, then the <tt>block</tt> is used as the message, and <tt>progname</tt> is used as the program name.
- !ruby/struct:SM::Flow::H 
  level: 3
  text: Examples
- !ruby/struct:SM::Flow::VERB 
  body: "  logger.info(&quot;MainApp&quot;) { &quot;Received connection from #{ip}&quot; }\n  # ...\n  logger.info &quot;Waiting for input from user&quot;\n  # ...\n  logger.info { &quot;User typed #{input}&quot; }\n"
- !ruby/struct:SM::Flow::P 
  body: You'll probably stick to the second form above, unless you want to provide a program name (which you can do with <tt>Logger#progname=</tt> as well).
- !ruby/struct:SM::Flow::H 
  level: 3
  text: Return
- !ruby/struct:SM::Flow::P 
  body: "See #add."
full_name: Logger#info
is_singleton: false
name: info
params: (progname = nil, &block)
visibility: public

X7ROOT File Manager

Editing: info-i.yaml

Upload File

Create Folder