logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

dot.1p (3464B)

    

  1. '\" et
  2. .TH DOT "1P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. dot
  12. \(em execute commands in the current environment
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. \&. \fIfile\fR
  17. .fi
  18. .SH DESCRIPTION
  19. The shell shall execute commands from the
  20. .IR file
  21. in the current environment.
  22. .P
  23. If
  24. .IR file
  25. does not contain a
  26. <slash>,
  27. the shell shall use the search path specified by
  28. .IR PATH
  29. to find the directory containing
  30. .IR file .
  31. Unlike normal command search, however, the file searched for by the
  32. .IR dot
  33. utility need not be executable. If no readable file is found, a
  34. non-interactive shell shall abort; an interactive shell shall write a
  35. diagnostic message to standard error, but this condition shall not be
  36. considered a syntax error.
  37. .SH OPTIONS
  38. None.
  39. .SH OPERANDS
  40. See the DESCRIPTION.
  41. .SH STDIN
  42. Not used.
  43. .SH "INPUT FILES"
  44. See the DESCRIPTION.
  45. .SH "ENVIRONMENT VARIABLES"
  46. See the DESCRIPTION.
  47. .SH "ASYNCHRONOUS EVENTS"
  48. Default.
  49. .SH STDOUT
  50. Not used.
  51. .SH STDERR
  52. The standard error shall be used only for diagnostic messages.
  53. .SH "OUTPUT FILES"
  54. None.
  55. .SH "EXTENDED DESCRIPTION"
  56. None.
  57. .SH "EXIT STATUS"
  58. If no readable file was found or if the commands in the file could not
  59. be parsed, and the shell is interactive (and therefore does not abort; see
  60. .IR "Section 2.8.1" ", " "Consequences of Shell Errors"),
  61. the exit status shall be non-zero. Otherwise, return the value of the
  62. last command executed, or a zero exit status if no command is executed.
  63. .SH "CONSEQUENCES OF ERRORS"
  64. Default.
  65. .LP
  66. .IR "The following sections are informative."
  67. .SH "APPLICATION USAGE"
  68. None.
  69. .SH EXAMPLES
  70. .LP
  71. .nf
  72. cat foobar
  73. \fBfoo=hello bar=world\fR
  74. \&. ./foobar
  75. echo $foo $bar
  76. \fBhello world\fR
  77. .fi
  78. .SH "RATIONALE"
  79. Some older implementations searched the current directory for the
  80. .IR file ,
  81. even if the value of
  82. .IR PATH
  83. disallowed it. This behavior was omitted from this volume of POSIX.1\(hy2017 due to concerns
  84. about introducing the susceptibility to trojan horses that the user
  85. might be trying to avoid by leaving
  86. .BR dot
  87. out of
  88. .IR PATH .
  89. .P
  90. The KornShell version of
  91. .IR dot
  92. takes optional arguments that are set to the positional parameters.
  93. This is a valid extension that allows a
  94. .IR dot
  95. script to behave identically to a function.
  96. .SH "FUTURE DIRECTIONS"
  97. None.
  98. .SH "SEE ALSO"
  99. .IR "Section 2.14" ", " "Special Built-In Utilities",
  100. .IR "\fIreturn\fR\^"
  101. .\"
  102. .SH COPYRIGHT
  103. Portions of this text are reprinted and reproduced in electronic form
  104. from IEEE Std 1003.1-2017, Standard for Information Technology
  105. -- Portable Operating System Interface (POSIX), The Open Group Base
  106. Specifications Issue 7, 2018 Edition,
  107. Copyright (C) 2018 by the Institute of
  108. Electrical and Electronics Engineers, Inc and The Open Group.
  109. In the event of any discrepancy between this version and the original IEEE and
  110. The Open Group Standard, the original IEEE and The Open Group Standard
  111. is the referee document. The original Standard can be obtained online at
  112. http://www.opengroup.org/unix/online.html .
  113. .PP
  114. Any typographical or formatting errors that appear
  115. in this page are most likely
  116. to have been introduced during the conversion of the source files to
  117. man page format. To report such errors, see
  118. https://www.kernel.org/doc/man-pages/reporting_bugs.html .