Changeset f208a1c
- Timestamp:
- 06/24/2005 02:52:13 PM (19 years ago)
- Branches:
- 6.1, 6.1.1
- Children:
- c5ec23b
- Parents:
- 74a8136
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r74a8136 rf208a1c 86 86 </listitem> 87 87 88 <listitem><para>June 23rd, 2005 [archaic]: Rewrote the inputrc page. 89 </para></listitem> 90 88 91 <listitem><para>June 22nd, 2005 [archaic]: Added a link to point to test 89 92 results.</para></listitem> -
chapter07/inputrc.xml
r74a8136 rf208a1c 10 10 <indexterm zone="ch-scripts-inputrc"><primary sortas="e-/etc/inputrc">/etc/inputrc</primary></indexterm> 11 11 12 <para>The <filename>/etc/inputrc</filename> file deals with mapping 13 the keyboard for specific situations. This file is the start-up file 14 used by <application>Readline</application>, the input-related 15 library used by <application>Bash</application> and most other 16 shells.</para> 12 <para>The <filename>inputrc</filename> file handles keyboard mapping for 13 specific situations. This file is the startup file used by Readline — the 14 input-related library — used by Bash and most other shells.</para> 17 15 18 <para>For more information, see the <command>bash</command> info page, section 19 <emphasis>Readline Init File</emphasis>. The 20 <filename class="libraryfile">readline</filename> info page is 21 also a good source of information.</para> 16 <para>Most people do not need user-specific keyboard mappings so the command 17 below creates a global <filename>/etc/inputrc</filename> used by everyone who 18 logs in. If you later decide you need to override the defaults on a per-user 19 basis, you can create a <filename>.inputrc</filename> file in the user's home 20 directory with the modified mappings.</para> 22 21 23 <para>Global values are set in <filename>/etc/inputrc</filename>. 24 Personal user values are set in <filename>~/.inputrc</filename>. The 25 <filename>~/.inputrc</filename> file will override the global settings 26 file. A later page sets up Bash to use 27 <filename>/etc/inputrc</filename> if there is no 28 <filename>.inputrc</filename> for a user when 29 <filename>/etc/profile</filename> is read (usually at login). To make 30 the system use both, or to negate global keyboard handling, it is a 31 good idea to place a default <filename>.inputrc</filename> into the 32 <filename class="directory">/etc/skel</filename> directory for use 33 with new users.</para> 22 <para>For more information on how to edit the inputrc file, see <command>info 23 bash</command> under the <emphasis>Readline Init File</emphasis> section. 24 <command>info readline</command> is also a good source of information.</para> 34 25 35 <para>Below is a base <filename>/etc/inputrc</filename>, along with 36 comments to explain what the various options do. Note that comments 37 cannot be on the same line as commands.</para> 38 39 <para>To create the <filename>.inputrc</filename> in <filename 40 class="directory">/etc/skel</filename> using the command below, change 41 the command's output to <filename 42 class="directory">/etc/skel/.inputrc</filename> and be sure to 43 check/set permissions afterward. Copy that file to 44 <filename>/etc/inputrc</filename> and the home directory of any user 45 already existing on the system, including <emphasis>root</emphasis>, 46 that needs a private version of the file. Be certain to use the 47 <parameter>-p</parameter> parameter of <command>cp</command> to 48 maintain permissions and be sure to change owner and group 49 appropriately.</para> 26 <para>Below is a generic global <filename>inputrc</filename> along with comments 27 to explain what the various options do. Note that comments cannot be on the same 28 line as commands. Create the file using the following command:</para> 50 29 51 30 <screen><userinput>cat > /etc/inputrc << "EOF" … … 53 32 # Modified by Chris Lynn <roryo@roryo.dynup.net> 54 33 55 # Make sure we don't output everything on the 1line34 # Allow the command prompt to wrap to the next line 56 35 set horizontal-scroll-mode Off 57 36 -
general.ent
r74a8136 rf208a1c 1 1 <?xml version="1.0" encoding="ISO-8859-1"?> 2 <!ENTITY version "TESTING-2005062 3">3 <!ENTITY releasedate "June 2 3, 2005">2 <!ENTITY version "TESTING-20050624"> 3 <!ENTITY releasedate "June 24, 2005"> 4 4 <!ENTITY milestone "6.1"> 5 5
Note:
See TracChangeset
for help on using the changeset viewer.