Systems Practical 2 Files, Editing, & Submitting

Total Page:16

File Type:pdf, Size:1020Kb

Systems Practical 2 Files, Editing, & Submitting Systems Practical 2 Files, Editing, & Submitting∗ Roger Burroughes This practical consists of three sections: • how to edit text files with Emacs • how to submit assignments electronically • how to use file permissions and related utilities Note, however, that it is important that you should complete the “submit” section of this practical. Leave yourself time to do this — even if it means not completing the other sections (although it is in your interest to try anything later, in your own time, that you do not finish in the lab session). ∗Version for 2006/2007 1 Editing Text With Emacs This section will give you some practice in using Emacs. It is divided into two parts: • The first section allows you to try out some of the Emacs commands described in the systems lecture. • In the second section, you will put these commands into practice by editing some text. Either by using some supplied text (a poem by Robert Burns), or by creating your own text (for example, by making notes on some aspect of the course, or on the emacs tutorial itself). Emacs Tutorial Choose one of the following methods to run the Emacs tutorial: Method 1: 1. Make sure you are in your home directory (type “cd” to return to your home directory if you’re not sure — and then “pwd” to check), then make a copy of the Emacs Tutorial, rename it and put it in your home directory as follows: cp ˜infteach/system/emacs-tutorial my-tutorial This takes a copy of the file emacs-tutorial, renames it my-tutorial, and places it in your home directory (assuming you are in your home directory, or have used “cd”). 2. Open the tutorial in Emacs by typing: emacs my-tutorial and work through the tutorial to the end. If there are any problems with, or comments on, or questions about the tutorial, make a note of them. Method 2: 1. Start emacs from the command line (just type “emacs” at the Unix prompt and hit “Return”) or Select “Emacs Text Editor” from the “Applications ⇒ Programming” menu. 2. Select “Emacs Tutorial” from the “Help” menu at the top of the Emacs window. To Quit: 1. When you’ve finished, type “Ctrl-x, Ctrl-s” to save it1, then “Ctrl-x, Ctrl-c” to quit. Practice In Using Emacs Make a copy of ˜infteach/system/poem in your home directory (use “cp ˜infteach/system/poem poem” from the command line — this will make a copy in your current working directory). Once you have done this, open the file with Emacs: % emacs poem 1If you selected the “Emacs Tutorial” from the “Help” menu, the file will be saved as “TUTORIAL” in your home directory. 2 (note that you get a new Emacs window, and no return of the Unix prompt in the invoking terminal window - you won’t get the prompt back until you quit Emacs). 1. You will see that the underlining of the title is mis-aligned. Move the cursor (using the mouse or emacs command keys) to the second line and insert the appropriate number of spaces in front of the underlining. If you put in more spaces than you meant to, you can remove the surplus with the “←−” (Backspace) key. 2. The first line of the seventh stanza (line 34 of the file) is incomplete. At the moment it reads: They’ve ta’en a weapon, and , It should read: They’ve ta’en a weapon, long and sharp, Insert the necessary words (use “Ctrl-U 3 4 Ctrl-N”2 to go to the correct line — assuming the cursor is at the top of the file, or use the mouse and cursor keys). 3. The eighth stanza is full of spelling mistakes — go through and correct them all (use spell-checking for this — see under “Other Useful Commands” in the reference section of the lecture notes). 4. The second last stanza has some (obvious!) rubbish at the end of it, so remove everything from “All of the next...” to “end of the junk”3. 5. The second and third stanzas are in the wrong order. Select the text to be moved (the second stanza and the blank line below it) by moving the cursor to the start of the second stanza, click and hold down the left mouse button, and drag the cursor down to the end of the stanza and release the button — you should see the text highlighted as you move, and it should stay highlighted when you release the mouse button. The highlighted lines are a “region”, and can be cut out of the file with “Ctrl-W”. You can then move the cursor to the first line of the fourth stanza and paste the text back in with “Ctrl-Y”. If you move the cursor after cutting, and before pasting, you can move regions of text around the file Take a look at the “Edit” menu. The “Cut” and “Paste” commands just used are duplicated here, as well as two related commands: • Copy lets you duplicate the selected region by making it available for pasting without having to cut it first. • Clear lets you remove the selected region by cutting it without making it available for pasting. Notice how the menu items are greyed out: they are not available for you to use when there is no region highlighted. There’s also the very useful “Undo” command in the “Edit” menu that will undo your last editing command. • Make some comments on your experiences with the Emacs tutorial, using any notes you took during the work-through above (or make some up — we only need text to type here!) Once you’ve finished, save your file and exit Emacs (see the “To Quit” section of the “Emacs Tutorial” section above). 2This is how you give a numeric argument, in this case “3 4” (for 34). The next command or keystroke is executed this number of times, in this case “Ctrl-N” (next line) so the cursor moves down 34 lines. 3Note that entire lines can be deleted with “Ctrl-K” (assuming you’re at the start of the line — otherwise “Ctrl-K” just deletes from the current cursor position to the end of the line). 3 Electronic Submission of Work This section demonstrates the “submit” command, used to submit coursework electronically. The requirement here is simple — to successfully use the submit command to submit the results of the Emacs4 practical. Once you have completed your work, and created a file containing your submission (let’s — for the sake of this example — call the file “submission”), you need to submit it with the submit command, and you will require the exercise (or practical) name (or code). For this exercise, the code is “se1” — the command should therefore be5: % submit inf1 inf1a se1 submission If you just type the command “submit” you will be given a list of the valid options (in the output below, long lines are truncated): % submit submit 2.63.1-1.dice.0 usage: to submit an exercise: submit <year> <course> <exercise-number> <file1> <file2>... where the <exercise-number> is some integer and <file> can be a regular file or a directory. You need to specify which year you are in. Valid ’Year’ choices are: msc (courses: vis-5 tts-5 tm-5 tdd spnlp-5 rl propm ppls-5 ... inf2 (courses: inf2d inf2c inf2b inf2a) inf1 (courses: inf1b inf1a) cs4 (courses: vis-4 tpl slip qsx ppls-4 pa-4 ms-4 hci-4 fpl... cs3 (courses: st seoc sdp pi os lsi ip fps ec dbs ct cs com... cs1 (courses: cpmt cp1 cl1) cg1 (courses: hc1 fmcs1) ai4 (courses: tts-4 tm-4 spnlp-4 masws-4 lfd-4 kmm-4 iar-4 ... ai3 (courses: pi lp kre ivr ics icl gagp ailp abs) test (courses: test5 test4 test3 test2 test1) SUBMISSION DID NOT HAPPEN! % If you get the exercise name (practical code) wrong (and can you see what’s wrong with the incorrect example command below?), you will see the following: % submit inf1 inf1a se2 submission submit 2.63.1-1.dice.0 usage: to submit an exercise: submit <year> <course> <exercise-number> <file1> <file2>... where the <exercise-number> is some integer and <file> can be a regular file or a directory. The exercise name should be one of: se1 fp4 fp3 fp2 fp1 cl4 cl3 cl2 cl1 for course inf1a of year inf1. 4If you do not complete the Emacs part of this practical, submitting any text file will do – the important thing is to successfully use the submit command, not what you actually submit! 5In these examples, the Unix prompt is represented by the % symbol. 4 SUBMISSION DID NOT HAPPEN! % Note that submit will always tell you if the submission completes or fails — you will see either “SUBMISSION DID NOT HAPPEN!” or “Submission... succeeded”. Using the earlier example (a file called ’submission’ from the home directory ’/home/infteach’, for the module ’inf1a’ and year ’inf1’, with exercise number ’se1’) we should see: % submit inf1 inf1a se1 submission Submit the following for exercise se1, module inf1a of the inf1 course. /amd/nfs/pegasus/disk/ptn041/infteach/submission Is this correct (y/n: n aborts)? y Submission of the following for exercise se1, module inf1a of the inf1 course succeeded: /amd/nfs/pegasus/disk/ptn041/infteach/submission % Note that you may see either the long or the short version of the pathname for your file echoed back in the response (in this example, either /amd/nfs/pegasus/disk/ptn041/infteach/submission or /home/infteach/submission). Either is OK — they both refer to the same file.
Recommended publications
  • Administering Unidata on UNIX Platforms
    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
    [Show full text]
  • Types and Programming Languages by Benjamin C
    < Free Open Study > . .Types and Programming Languages by Benjamin C. Pierce ISBN:0262162091 The MIT Press © 2002 (623 pages) This thorough type-systems reference examines theory, pragmatics, implementation, and more Table of Contents Types and Programming Languages Preface Chapter 1 - Introduction Chapter 2 - Mathematical Preliminaries Part I - Untyped Systems Chapter 3 - Untyped Arithmetic Expressions Chapter 4 - An ML Implementation of Arithmetic Expressions Chapter 5 - The Untyped Lambda-Calculus Chapter 6 - Nameless Representation of Terms Chapter 7 - An ML Implementation of the Lambda-Calculus Part II - Simple Types Chapter 8 - Typed Arithmetic Expressions Chapter 9 - Simply Typed Lambda-Calculus Chapter 10 - An ML Implementation of Simple Types Chapter 11 - Simple Extensions Chapter 12 - Normalization Chapter 13 - References Chapter 14 - Exceptions Part III - Subtyping Chapter 15 - Subtyping Chapter 16 - Metatheory of Subtyping Chapter 17 - An ML Implementation of Subtyping Chapter 18 - Case Study: Imperative Objects Chapter 19 - Case Study: Featherweight Java Part IV - Recursive Types Chapter 20 - Recursive Types Chapter 21 - Metatheory of Recursive Types Part V - Polymorphism Chapter 22 - Type Reconstruction Chapter 23 - Universal Types Chapter 24 - Existential Types Chapter 25 - An ML Implementation of System F Chapter 26 - Bounded Quantification Chapter 27 - Case Study: Imperative Objects, Redux Chapter 28 - Metatheory of Bounded Quantification Part VI - Higher-Order Systems Chapter 29 - Type Operators and Kinding Chapter 30 - Higher-Order Polymorphism Chapter 31 - Higher-Order Subtyping Chapter 32 - Case Study: Purely Functional Objects Part VII - Appendices Appendix A - Solutions to Selected Exercises Appendix B - Notational Conventions References Index List of Figures < Free Open Study > < Free Open Study > Back Cover A type system is a syntactic method for automatically checking the absence of certain erroneous behaviors by classifying program phrases according to the kinds of values they compute.
    [Show full text]
  • UNIX Workshop Series: Quick-Start Objectives
    Part I UNIX Workshop Series: Quick-Start Objectives Overview – Connecting with ssh Command Window Anatomy Command Structure Command Examples Getting Help Files and Directories Wildcards, Redirection and Pipe Create and edit files Overview Connecting with ssh Open a Terminal program Mac: Applications > Utilities > Terminal ssh –Y [email protected] Linux: In local shell ssh –Y [email protected] Windows: Start Xming and PuTTY Create a saved session for the remote host name centos.css.udel.edu using username Connecting with ssh First time you connect Unix Basics Multi-user Case-sensitive Bash shell, command-line Commands Command Window Anatomy Title bar Click in the title bar to bring the window to the front and make it active. Command Window Anatomy Login banner Appears as the first line of a login shell. Command Window Anatomy Prompts Appears at the beginning of a line and usually ends in $. Command Window Anatomy Command input Place to type commands, which may have options and/or arguments. Command Window Anatomy Command output Place for command response, which may be many lines long. Command Window Anatomy Input cursor Typed text will appear at the cursor location. Command Window Anatomy Scroll Bar Will appear as needed when there are more lines than fit in the window. Command Window Anatomy Resize Handle Use the mouse to change the window size from the default 80x24. Command Structure command [arguments] Commands are made up of the actual command and its arguments. command -options [arguments] The arguments are further broken down into the command options which are single letters prefixed by a “-” and other arguments that identify data for the command.
    [Show full text]
  • System Log Commands
    System Log Commands • system set-log , on page 2 • show system logging-level, on page 3 • show log, on page 4 System Log Commands 1 System Log Commands system set-log system set-log To set the log level and log type of messages, use the system set-log command in privileged EXEC mode. system set-log level {debug | info | warning | error | critical} logtype {configuration | operational | all} Syntax Description level Specifies the log level. debug Logs all messages. info Logs all messages that have info and higher severity level. warning Logs all messages that have warning and higher severity level. error Logs all messages that have error and higher severity level. critical Logs all messages that have critical severity level. logtype Specifies the log type. configuration Configuration log messages are recorded. operational Operational log messages are recorded. all All types of log messages are recorded. Command Default For the configuration log, info is the default level. For the operational log, warning is the default level. Command Modes Privileged EXEC (#) Command History Release Modification 3.5.1 This command was introduced. Usage Guidelines After a system reboot, the modified logging configuration is reset to the default level, that is, info for the configuration log and warning for the operational log. Example The following example shows how to configure a log level: nfvis# system set-log level error logtype all System Log Commands 2 System Log Commands show system logging-level show system logging-level To view the log level and log type settings, use the show system logging-level command in privileged EXEC mode.
    [Show full text]
  • Dell EMC Powerstore CLI Guide
    Dell EMC PowerStore CLI Guide May 2020 Rev. A01 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Contents Additional Resources.......................................................................................................................4 Chapter 1: Introduction................................................................................................................... 5 Overview.................................................................................................................................................................................5 Use PowerStore CLI in scripts.......................................................................................................................................5 Set up the PowerStore CLI client........................................................................................................................................5 Install the PowerStore CLI client..................................................................................................................................
    [Show full text]
  • Epmp Command Line Interface User Guide
    USER GUIDE ePMP Command Line Interface ePMP Command Line Interface User Manual Table of Contents 1 Introduction ...................................................................................................................................... 3 1.1 Purpose ................................................................................................................................ 3 1.2 Command Line Access ........................................................................................................ 3 1.3 Command usage syntax ...................................................................................................... 3 1.4 Basic information ................................................................................................................. 3 1.4.1 Context sensitive help .......................................................................................................... 3 1.4.2 Auto-completion ................................................................................................................... 3 1.4.3 Movement keys .................................................................................................................... 3 1.4.4 Deletion keys ....................................................................................................................... 4 1.4.5 Escape sequences .............................................................................................................. 4 2 Command Line Interface Overview ..............................................................................................
    [Show full text]
  • Powerview Command Reference
    PowerView Command Reference TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... PowerView User Interface ............................................................................................................ PowerView Command Reference .............................................................................................1 History ...................................................................................................................................... 12 ABORT ...................................................................................................................................... 13 ABORT Abort driver program 13 AREA ........................................................................................................................................ 14 AREA Message windows 14 AREA.CLEAR Clear area 15 AREA.CLOSE Close output file 15 AREA.Create Create or modify message area 16 AREA.Delete Delete message area 17 AREA.List Display a detailed list off all message areas 18 AREA.OPEN Open output file 20 AREA.PIPE Redirect area to stdout 21 AREA.RESet Reset areas 21 AREA.SAVE Save AREA window contents to file 21 AREA.Select Select area 22 AREA.STDERR Redirect area to stderr 23 AREA.STDOUT Redirect area to stdout 23 AREA.view Display message area in AREA window 24 AutoSTOre ..............................................................................................................................
    [Show full text]
  • Useful Commands in Linux and Other Tools for Quality Control
    Useful commands in Linux and other tools for quality control Ignacio Aguilar INIA Uruguay 05-2018 Unix Basic Commands pwd show working directory ls list files in working directory ll as before but with more information mkdir d make a directory d cd d change to directory d Copy and moving commands To copy file cp /home/user/is . To copy file directory cp –r /home/folder . to move file aa into bb in folder test mv aa ./test/bb To delete rm yy delete the file yy rm –r xx delete the folder xx Redirections & pipe Redirection useful to read/write from file !! aa < bb program aa reads from file bb blupf90 < in aa > bb program aa write in file bb blupf90 < in > log Redirections & pipe “|” similar to redirection but instead to write to a file, passes content as input to other command tee copy standard input to standard output and save in a file echo copy stream to standard output Example: program blupf90 reads name of parameter file and writes output in terminal and in file log echo par.b90 | blupf90 | tee blup.log Other popular commands head file print first 10 lines list file page-by-page tail file print last 10 lines less file list file line-by-line or page-by-page wc –l file count lines grep text file find lines that contains text cat file1 fiel2 concatenate files sort sort file cut cuts specific columns join join lines of two files on specific columns paste paste lines of two file expand replace TAB with spaces uniq retain unique lines on a sorted file head / tail $ head pedigree.txt 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10
    [Show full text]
  • A Brief Introduction to Unix-2019-AMS
    A Brief Introduction to Linux/Unix – AMS 2019 Pete Pokrandt UW-Madison AOS Systems Administrator [email protected] Twitter @PTH1 Brief Intro to Linux/Unix o Brief History of Unix o Basics of a Unix session o The Unix File System o Working with Files and Directories o Your Environment o Common Commands Brief Intro to Unix (contd) o Compilers, Email, Text processing o Image Processing o The vi editor History of Unix o Created in 1969 by Kenneth Thompson and Dennis Ritchie at AT&T o Revised in-house until first public release 1977 o 1977 – UC-Berkeley – Berkeley Software Distribution (BSD) o 1983 – Sun Workstations produced a Unix Workstation o AT&T unix -> System V History of Unix o Today – two main variants, but blended o System V (Sun Solaris, SGI, Dec OSF1, AIX, linux) o BSD (Old SunOS, linux, Mac OSX/MacOS) History of Unix o It’s been around for a long time o It was written by computer programmers for computer programmers o Case sensitive, mostly lowercase abbreviations Basics of a Unix Login Session o The Shell – the command line interface, where you enter commands, etc n Some common shells Bourne Shell (sh) C Shell (csh) TC Shell (tcsh) Korn Shell (ksh) Bourne Again Shell (bash) [OSX terminal] Basics of a Unix Login Session o Features provided by the shell n Create an environment that meets your needs n Write shell scripts (batch files) n Define command aliases n Manipulate command history n Automatically complete the command line (tab) n Edit the command line (arrow keys in tcsh) Basics of a Unix Login Session o Logging in to a unix
    [Show full text]
  • UNIX (Solaris/Linux) Quick Reference Card Logging in Directory Commands at the Login: Prompt, Enter Your Username
    UNIX (Solaris/Linux) QUICK REFERENCE CARD Logging In Directory Commands At the Login: prompt, enter your username. At the Password: prompt, enter ls Lists files in current directory your system password. Linux is case-sensitive, so enter upper and lower case ls -l Long listing of files letters as required for your username, password and commands. ls -a List all files, including hidden files ls -lat Long listing of all files sorted by last Exiting or Logging Out modification time. ls wcp List all files matching the wildcard Enter logout and press <Enter> or type <Ctrl>-D. pattern Changing your Password ls dn List files in the directory dn tree List files in tree format Type passwd at the command prompt. Type in your old password, then your new cd dn Change current directory to dn password, then re-enter your new password for verification. If the new password cd pub Changes to subdirectory “pub” is verified, your password will be changed. Many systems age passwords; this cd .. Changes to next higher level directory forces users to change their passwords at predetermined intervals. (previous directory) cd / Changes to the root directory Changing your MS Network Password cd Changes to the users home directory cd /usr/xx Changes to the subdirectory “xx” in the Some servers maintain a second password exclusively for use with Microsoft windows directory “usr” networking, allowing you to mount your home directory as a Network Drive. mkdir dn Makes a new directory named dn Type smbpasswd at the command prompt. Type in your old SMB passwword, rmdir dn Removes the directory dn (the then your new password, then re-enter your new password for verification.
    [Show full text]
  • SPELL-2 Manual.Pdf
    Julie J. Masterson, PhD • Kenn Apel, PhD • Jan Wasowicz, PhD © 2002, 2006 by Learning By Design, Inc. All rights reserved. No part of this publication may be reproduced in whole or in part without the prior written permission of Learning By Design, Inc. SPELL: Spelling Performance Evaluation for Language and Literacy and Learning By Design, Inc. are registered trademarks, and Making A Difference in K-12 Education is a trademark of Learning By Design, Inc. 13 12 11 10 09 08 07 06 8 7 6 5 4 3 2 1 ISBN-13: 978-0-9715133-2-7 ISBN-10: 0-9715133-2-5 Printed in the United States of America P.O. Box 5448 Evanston, IL 60604-5448 www.learningbydesign.com Information & Customer Services For answers to Frequently Asked Questions about SPELL–2, please visit the Learning By Design, Inc., website at www.learningbydesign.com. Technical Support First, please visit the technical support FAQ page at www.learningbydesign.com. If you don’t find an answer to your question, please call 1-847-328-8390 between 8 am and 5 pm CST. We’d love to hear from you! Your feedback, comments, and suggestions are always welcome. Please contact us by email at [email protected]. Portions of code are Copyright © 1994–2002 Integrations New Media, Inc., and used under license by Integration New Media, Inc. DIRECTOR® © 1984–2004 Macromedia, Inc. DIBELS is a registered trademark of Dynamic Measurement Group, Inc., and is not affiliated with Learning By Design, Inc. Earobics® is a product and registered trademark of Cognitive Concepts, Inc., a division of Houghton-Mifflin, and is not affiliated with Learning By Design, Inc.
    [Show full text]
  • Gnu Coreutils Core GNU Utilities for Version 5.93, 2 November 2005
    gnu Coreutils Core GNU utilities for version 5.93, 2 November 2005 David MacKenzie et al. This manual documents version 5.93 of the gnu core utilities, including the standard pro- grams for text and file manipulation. Copyright c 1994, 1995, 1996, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. Chapter 1: Introduction 1 1 Introduction This manual is a work in progress: many sections make no attempt to explain basic concepts in a way suitable for novices. Thus, if you are interested, please get involved in improving this manual. The entire gnu community will benefit. The gnu utilities documented here are mostly compatible with the POSIX standard. Please report bugs to [email protected]. Remember to include the version number, machine architecture, input files, and any other information needed to reproduce the bug: your input, what you expected, what you got, and why it is wrong. Diffs are welcome, but please include a description of the problem as well, since this is sometimes difficult to infer. See section “Bugs” in Using and Porting GNU CC. This manual was originally derived from the Unix man pages in the distributions, which were written by David MacKenzie and updated by Jim Meyering.
    [Show full text]