Sponsored Content
Full Discussion: Gud to read u r Thread
Contact Us Post Here to Contact Site Administrators and Moderators Gud to read u r Thread Post 302568689 by DukeNuke2 on Friday 28th of October 2011 02:51:17 AM
Old 10-28-2011
Hello,

Per our forum rules, all users must write in English, use semi-formal or formal English language and style, and correct spelling errors.

The reason for this is that most software and operating systems are written in English and these are software related technical forums.

In addition, nearly 95% of all visitors to this site come here because they are referred by a search engine. In order for future searches on your post (with answers) to work well, you need to spell correctly!

So, as a benefit and courtesy to current and future knowledge seekers, please be careful with your language, check your spelling and correct your spelling errors. You might receive a forum infraction if you don't pay attention to this.

Also, do not write in cyberpunk or abbreviated chat style under any circumstances and do not use profanity. This is not a chat room, it is a formal knowledge base to serve you and everyone, of all ages and cultural backgrounds.

Thanks!

The UNIX and Linux Forums
 

2 More Discussions You Might Find Interesting

1. Programming

How to implement read/write thread

How to implement read/write thread. This has to implemented at server side ar at client side? (1 Reply)
Discussion started by: shilpi_gup
1 Replies

2. Shell Programming and Scripting

Read from a file in unix(Continue from previous thread)

Hi This is continuation of previos thread status=running username=abc password=123456 server=linux The script was made which is used to capture the data from file ./scr test status It will give result running I have a case like status = running username=abc password=123456... (14 Replies)
Discussion started by: parthmittal2007
14 Replies
spell(1)							   User Commands							  spell(1)

NAME
spell, hashmake, spellin, hashcheck - report spelling errors SYNOPSIS
spell [-bilvx] [+ local_file] [file] ... /usr/lib/spell/hashmake /usr/lib/spell/spellin n /usr/lib/spell/hashcheck spelling_list DESCRIPTION
The spell command collects words from the named files and looks them up in a spelling list. Words that neither occur among nor are deriv- able (by applying certain inflections, prefixes, or suffixes) from words in the spelling list are written to the standard output. If there are no file arguments, words to check are collected from the standard input. spell ignores most troff(1), tbl(1), and eqn(1) con- structs. Copies of all output words are accumulated in the history file (spellhist), and a stop list filters out misspellings (for example, their=thy-y+ier) that would otherwise pass. By default, spell (like deroff(1)) follows chains of included files (.so and .nx troff(1) requests), unless the names of such included files begin with /usr/lib. The standard spelling list is based on many sources, and while more haphazard than an ordinary dictionary, is also more effective in respect to proper names and popular technical words. Coverage of the specialized vocabularies of biology, medicine and chemistry is light. Three programs help maintain and check the hash lists used by spell: hashmake Reads a list of words from the standard input and writes the corresponding nine-digit hash code on the standard output. spellin Reads n hash codes from the standard input and writes a compressed spelling list on the standard output. hashcheck Reads a compressed spelling_list and recreates the nine-digit hash codes for all the words in it. It writes these codes on the standard output. OPTIONS
The following options are supported: -b Check British spelling. Besides preferring centre, colour, programme, speciality, travelled, and so forth, this option insists upon -ise in words like standardise. -i Cause deroff(1) to ignore .so and .nx commands. If deroff(1) is not present on the system, then this option is ignored. -l Follow the chains of all included files. -v Print all words not literally in the spelling list, as well as plausible derivations from the words in the spelling list. -x Print every plausible stem, one per line, with = preceding each word. +local_file Specify a set of words that are correct spellings (in addition to spell's own spelling list) for each job. local_file is the name of a user-provided file that contains a sorted list of words, one per line. Words found in local_file are removed from spell's output. Use sort(1) to order local_file in ASCII collating sequence. If this ordering is not followed, some entries in local_file might be ignored. OPERANDS
The following operands are supported: file A path name of a text file to check for spelling errors. If no files are named, words are collected from the standard input. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of spell: LC_CTYPE, LC_MESSAGES, and NLSPATH. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. FILES
D_SPELL=/usr/lib/spell/hlist[ab] hashed spelling lists, American & British S_SPELL=/usr/lib/spell/hstop hashed stop list H_SPELL=/var/adm/spellhist history file /usr/share/lib/dict/words master dictionary ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ SEE ALSO
deroff(1), eqn(1), sort(1), tbl(1), troff(1), attributes(5), environ(5) NOTES
spell works only on English words defined in the U.S. ASCII codeset. Because copies of all output are accumulated in the spellhist file, spellhist might grow quite large and require purging. BUGS
The spelling list's coverage is uneven. New installations might wish to monitor the output for several months to gather local additions. British spelling was done by an American. SunOS 5.11 23 spell(1)
All times are GMT -4. The time now is 10:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy