Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

program_invocation_short_name(3) [xfree86 man page]

INVOCATION_NAME(3)					     Linux Programmer's Manual						INVOCATION_NAME(3)

NAME
program_invocation_name, program_invocation_short_name - obtain name used to invoke calling program SYNOPSIS
#define _GNU_SOURCE /* See feature_test_macros(7) */ #include <errno.h> extern char *program_invocation_name; extern char *program_invocation_short_name; DESCRIPTION
program_invocation_name contains the name that was used to invoke the calling program. This is the same as the value of argv[0] in main(), with the difference that the scope of program_invocation_name is global. program_invocation_short_name contains the basename component of name that was used to invoke the calling program. That is, it is the same value as program_invocation_name, with all text up to and including the final slash (/), if any, removed. These variables are automatically initialized by the glibc run-time startup code. CONFORMING TO
These variables are GNU extensions, and should not be used in programs intended to be portable. NOTES
The Linux-specific /proc/[number]/cmdline file provides access to similar information. SEE ALSO
proc(5) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. GNU
2017-09-15 INVOCATION_NAME(3)

Check Out this Related Man Page

INVOCATION_NAME(3)					     Linux Programmer's Manual						INVOCATION_NAME(3)

NAME
program_invocation_name, program_invocation_short_name - obtain name used to invoke calling program SYNOPSIS
#define _GNU_SOURCE /* See feature_test_macros(7) */ #include <errno.h> extern char *program_invocation_name; extern char *program_invocation_short_name; DESCRIPTION
program_invocation_name contains the name that was used to invoke the calling program. This is the same as the value of argv[0] in main(), with the difference that the scope of program_invocation_name is global. program_invocation_short_name contains the basename component of name that was used to invoke the calling program. That is, it is the same value as program_invocation_name, with all text up to and including the final slash (/), if any, removed. These variables are automatically initialized by the glibc run-time startup code. CONFORMING TO
These variables are GNU extensions, and should not be used in programs intended to be portable. NOTES
The Linux-specific /proc/[number]/cmdline file provides access to similar information. SEE ALSO
proc(5) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. GNU
2017-09-15 INVOCATION_NAME(3)
Man Page

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

No xorg.conf or XF86Config

There is no xorg.conf file and no XF86Config file on a certain FreeBSD machine: # locate xorg.conf /usr/local/man/man5/xorg.conf.5.gz # locate XF86Config # Can someone let me know if that means that there is a bare bones set up possible only? xrandr works fine, but I am looking for ways to... (6 Replies)
Discussion started by: figaro
6 Replies

2. Shell Programming and Scripting

Can a script resize it's own mintty console?

I'm looking for finer granularity than the 20 ANSI escape sequence screen modes. What I'd like to do is have the terminal increase it's own height when I have to show the user a long menu. Platform is Cygwin 64 running over Win 7 Pro. Mike (4 Replies)
Discussion started by: Michael Stora
4 Replies

3. UNIX for Advanced & Expert Users

Shopt -s histappend

What is the point of this? Whenever I close my shell it appends to the history file without adding this. I have never seen it overwrite my history file. # When the shell exits, append to the history file instead of overwriting it shopt -s histappend (3 Replies)
Discussion started by: cokedude
3 Replies

4. Fedora

Fedora 30 and Slackware 14.2, how to obtain the same rendering?

Look this very good rendering on Slackware 14.2 in my opinion is near perfect. https://i.stack.imgur.com/q5trL.png Now look the same page on Fedora 30 https://i.stack.imgur.com/FBQv7.png In my opinion the fonts on Fedora are too small and difficult to read, I prefer the fat fonts of... (20 Replies)
Discussion started by: Linusolaradm1
20 Replies