Home
last modified time | relevance | path

Searched refs:message (Results 1 – 21 of 21) sorted by relevance

/manual/
A Dmessage.texi14 really big with dozens of message sets.
31 of the message handling functions are
64 message catalogs is always the same.
76 * The message catalog files:: Format of the message catalog files.
252 message catalog.
283 pair of set and message numbers.
324 @node The message catalog files
580 message numbers.
651 the name of the message set plus the name of the message or the special
1034 as long as no new message catalog is loaded the translation of a message
[all …]
A Dsyslog.texi75 Klogd then passes everything in the message ring to it.
228 does not write the message to Standard Error.
395 The message says the system is unusable.
397 Action on the message must be taken immediately.
399 The message states a critical condition.
401 The message describes an error.
403 The message is a warning.
405 The message describes a normal but important event.
407 The message is purely informational.
409 The message is only for debugging purposes.
[all …]
A Dargp.texi185 this parser. This is only used to print the @samp{Usage:} message. If
192 after the options in a long help message, with the two sections
284 In a long help message, options are sorted alphabetically within each
688 --help}} message, and terminates the program with an exit status of
854 message is produced. @xref{Argp Help Flags}.
987 Turns off any message-printing/exiting options, specifically
1071 This outputs a help message for the argp parser @var{argp} to
1096 A unix @samp{Usage:} message that explicitly lists all options.
1128 A message that prints where to report bugs for this program, if the
1188 do much except give an error message and exit when there are any
[all …]
A Derrno.texi12 file was actually opened correctly, and print an error message or take
455 The size of a message sent on a socket was larger than the supported
836 @errno{EBADMSG, 107, Bad message}
861 @errno{ENOMSG, 112, No message of desired type}
1143 @code{strerror} and @code{perror} give you the standard error message
1155 message string. The return value is a pointer to this string.
1188 @deftypefun void perror (const char *@var{message})
1194 This function prints an error message to the stream @code{stderr};
1198 If you call @code{perror} with a @var{message} that is either a null
1202 If you supply a non-null @var{message} argument, then @code{perror}
[all …]
A Dtexinfo.tex997 \message{pdf,}
1800 \message{fonts,}
2592 \message{markup,}
3336 \message{glyphs,}
3928 \message{tables,}
4758 \message{indexing,}
6030 \message{sectioning,}
6738 \message{toc,}
7608 \message{defuns,}
8013 \message{macros,}
[all …]
A Dpattern.texi1105 below). You can use @code{regerror} to produce an error message string
1457 error message string describing the reason for a nonzero value;
1621 the function @code{regerror} to turn it into an error message string.
1627 This function produces an error message string for the error code
1633 meaningful error message, but it might not be as detailed.
1635 If the error message can't fit in @var{length} bytes (including a
1641 store the entire error message. If this is less than @var{length}, then
1642 the error message was not truncated, and you can use it. Otherwise, you
1646 allocates a buffer for the error message:
2168 @item $@{@var{variable}:?@var{message}@}
[all …]
A Dsocket.texi85 destination address for each message you send.
206 should be prepared to read the entire message packet in a single call
207 to @code{read}; if it only reads part of the message, the remainder of
208 the message is simply discarded instead of being available for
1026 This constant is the address you use to send a broadcast message.
2705 message is too large for this to be possible.
2805 Don't include routing information in the message. This is only
2837 gotten a message from a client. It does close the socket for that
3179 messages to arrive, bouncing each message back to the sender.
3195 a message back to the client. Since the socket has no associated
[all …]
A Dsignal.texi192 signal, the shell typically prints some kind of error message.
238 * Signal Messages:: Printing a message describing a signal.
825 that terminated a child process. The clean way to print a message
849 containing a message describing the signal @var{signum}. You
859 @deftypefun void psignal (int @var{signum}, const char *@var{message})
870 If you call @code{psignal} with a @var{message} that is either a null
871 pointer or an empty string, @code{psignal} just prints the message
874 If you supply a non-null @var{message} argument, then @code{psignal}
876 character to separate the @var{message} from the string corresponding
886 This function returns the message describing the signal @var{signum} or
[all …]
A Dlocale.texi169 interface for message translation (@pxref{The Uniforum approach};
187 When developing the message translation functions it was felt that the
1137 message translation, and is better handled by the message
1140 The use of this symbol is deprecated. Instead message translation
1146 The use of this symbol is deprecated. Instead message translation
A Dgetopt.texi26 error message to the standard error stream if it encounters an unknown
129 prints an error message.
A Dstdio.texi1034 puts ("This is a message.");
1346 message.
1953 number, instead of a (possibly translated) error message.
2445 /* @r{Construct a message describing the value of a variable}
2886 @r{If not, return 0 after printing an error message.} */
3857 input with a comprehensible error message, not with a crash.
5242 Display the message in standard error.
5244 Display the message on the system console.
5274 message. Exactly one of the following values can be used:
5381 somehow else invalid, no part of the message is masked out.
[all …]
A DMakefile38 message search pattern io stdio llio filesys \
A Dlang.texi36 provides a convenient way to abort the program while printing a message
60 program (@pxref{Aborting a Program}) after printing a message of the
100 after printing a message of the form:
A Dmemory.texi871 message. Often it is convenient to write and use subroutines,
873 that take care of the error message
1281 default function which prints a message and calls @code{abort}
1744 trace file @file{log}. The message printed by @code{mtrace} shows there
2033 memory. The default action is to print a message and abort.
2796 fails. If the file cannot be opened, it prints an error message and
2832 don't get a clean error message. Instead you get a fatal signal like
3732 warn you. It is called with a string (a warning message) as argument.
A Dstartup.texi636 looks for message translation catalogs.
983 When this program is executed, it just prints the message and exits.
A Dinstall.texi664 and if you change any of the message translation files you will need
A Dfilesys.texi2253 be implemented as objects in the filesystem. These are message queues,
2263 If the system implements POSIX message queues as distinct objects and the
2264 file is a message queue object, this macro returns a non-zero value.
A Dterminal.texi1481 The STATUS character's effect is to print out a status message about how
A Dllio.texi2150 such as the presence of an urgent message on a socket. (@xref{Sockets},
/manual/examples/
A Dfilesrv.c31 char message[MAXMSG]; in main() local
45 nbytes = recvfrom (sock, message, MAXMSG, 0, in main()
54 fprintf (stderr, "Server: got message: %s\n", message); in main()
57 nbytes = sendto (sock, message, nbytes, 0, in main()
A Dfilecli.c35 char message[MAXMSG]; in main() local
58 nbytes = recvfrom (sock, message, MAXMSG, 0, NULL, 0); in main()
66 fprintf (stderr, "Client: got message: %s\n", message); in main()

Completed in 107 milliseconds