emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/lispref/os.texi [lexbind]


From: Miles Bader
Subject: [Emacs-diffs] Changes to emacs/lispref/os.texi [lexbind]
Date: Thu, 20 Nov 2003 19:36:48 -0500

Index: emacs/lispref/os.texi
diff -c emacs/lispref/os.texi:1.48.2.2 emacs/lispref/os.texi:1.48.2.3
*** emacs/lispref/os.texi:1.48.2.2      Tue Oct 14 19:10:12 2003
--- emacs/lispref/os.texi       Thu Nov 20 19:35:47 2003
***************
*** 590,596 ****
  
    Emacs provides access to variables in the operating system environment
  through various functions.  These variables include the name of the
! system, the user's @sc{uid}, and so on.
  
  @defvar system-configuration
  This variable holds the GNU configuration name for the hardware/software
--- 590,596 ----
  
    Emacs provides access to variables in the operating system environment
  through various functions.  These variables include the name of the
! system, the user's @acronym{UID}, and so on.
  
  @defvar system-configuration
  This variable holds the GNU configuration name for the hardware/software
***************
*** 820,826 ****
  @end defun
  
  @defun emacs-pid
! This function returns the process @sc{id} of the Emacs process.
  @end defun
  
  @defvar tty-erase-char
--- 820,826 ----
  @end defun
  
  @defun emacs-pid
! This function returns the process @acronym{ID} of the Emacs process.
  @end defun
  
  @defvar tty-erase-char
***************
*** 870,876 ****
  which the user is logged in.  If the environment variable @code{LOGNAME}
  is set, that value is used.  Otherwise, if the environment variable
  @code{USER} is set, that value is used.  Otherwise, the value is based
! on the effective @sc{uid}, not the real @sc{uid}.
  
  If you specify @var{uid}, the value is the user name that corresponds
  to @var{uid} (which should be an integer).
--- 870,876 ----
  which the user is logged in.  If the environment variable @code{LOGNAME}
  is set, that value is used.  Otherwise, if the environment variable
  @code{USER} is set, that value is used.  Otherwise, the value is based
! on the effective @acronym{UID}, not the real @acronym{UID}.
  
  If you specify @var{uid}, the value is the user name that corresponds
  to @var{uid} (which should be an integer).
***************
*** 885,891 ****
  
  @defun user-real-login-name
  This function returns the user name corresponding to Emacs's real
! @sc{uid}.  This ignores the effective @sc{uid} and ignores the
  environment variables @code{LOGNAME} and @code{USER}.
  @end defun
  
--- 885,891 ----
  
  @defun user-real-login-name
  This function returns the user name corresponding to Emacs's real
! @acronym{UID}.  This ignores the effective @acronym{UID} and ignores the
  environment variables @code{LOGNAME} and @code{USER}.
  @end defun
  
***************
*** 921,927 ****
  Titles}).
  
  @defun user-real-uid
! This function returns the real @sc{uid} of the user.
  The value may be a floating point number.
  
  @example
--- 921,927 ----
  Titles}).
  
  @defun user-real-uid
! This function returns the real @acronym{UID} of the user.
  The value may be a floating point number.
  
  @example
***************
*** 933,939 ****
  @end defun
  
  @defun user-uid
! This function returns the effective @sc{uid} of the user.
  The value may be a floating point number.
  @end defun
  
--- 933,939 ----
  @end defun
  
  @defun user-uid
! This function returns the effective @acronym{UID} of the user.
  The value may be a floating point number.
  @end defun
  
***************
*** 1935,1941 ****
  @code{C-s} and @kbd{C-q} for flow control.  Therefore, the choice of
  @kbd{C-s} and @kbd{C-q} as command characters for searching and quoting
  was natural and uncontroversial.  With so many commands needing key
! assignments, of course we assigned meanings to nearly all @sc{ascii}
  control characters.
  
    Later, some terminals were introduced which required these characters
--- 1935,1941 ----
  @code{C-s} and @kbd{C-q} for flow control.  Therefore, the choice of
  @kbd{C-s} and @kbd{C-q} as command characters for searching and quoting
  was natural and uncontroversial.  With so many commands needing key
! assignments, of course we assigned meanings to nearly all @acronym{ASCII}
  control characters.
  
    Later, some terminals were introduced which required these characters




reply via email to

[Prev in Thread] Current Thread [Next in Thread]