Look up More or more in Wiktionary, the free dictionary.

More or Mores may refer to:

Computers[link]

• MORE (application), a Mac OS outliner application
• more (command), a shell command
• MORE protocol, a routing protocol

Film[link]

• More (1969 film), a 1969 film directed by Barbet Schroeder
• More (1998 film), a short film by Mark Osborne

Language and culture[link]

• Morè (clan), a Maratha clan of India
• Mores, strongly held norms or customs
• Mòoré language or Moré, a language spoken primarily in Burkina Faso by the Mossi
• Moré, one of the 36 official languages of Bolivia

Magazines[link]

• More!, a British women's fashion magazine
• More (magazine), an American women's lifestyle magazine
• More (Punk magazine from Belgium)

Music[link]

• More (British band), a 1980s heavy metal band
• More (Croatian band), a 1980s band featuring Doris Dragović

Albums[link]

• More! (album), by Booka Shade, 2010
• More (Mary Alessi album), 2005
• More... (Montell Jordan album), 1996
• More (Tamia album), or the title song, 2004
• More... (Trace Adkins album), or the title song (see below), 1999
• More (Vitamin C album), 2001
• Soundtrack from the Film More, by Pink Floyd with music from the 1969 film (see above)
• More, by Mylon LeFevre, 1983
• More, by Resin Dogs, 2007

Songs[link]

• "More" (1956 song), written by Alex Alstone and Tom Glazer, popularized by Perry Como
• "More" (Mondo Cane theme), the theme from the 1963 film Mondo Cane
• "More" (Matthew West song)
• "More" (Peaches song)
• "More" (The Sisters of Mercy song)
• "More" (Trace Adkins song)
• "More" (Usher song)
• "More", by The Black Eyed Peas, performed on the Black Blue & You Tour
• "More", by Doctor and the Medics from I Keep Thinking It's Tuesday
• "More", by Junkie XL from More More
• "More", written by Stephen Sondheim and performed by Madonna on I'm Breathless
• "More", by Selena Gomez & the Scene from Kiss & Tell

Radio[link]

• More FM, a New Zealand radio network
• More Radio, an FM station in Swindon, North Wiltshire, UK
• The Breeze (Frome & West Wiltshire), formerly "More Radio", an FM Station in West Wiltshire and Frome in East Somerset, UK

Other[link]

• More (cigarette), a cigarette brand marketed to women
• More (store), a chain of supermarkets in India operated by the Aditya Birla Group
• More (surname), a family name, including a list of people with the surname
• Mores (SS), a comune (municipality) in the Province of Sassari, Sardinia, Italy
• More, Shropshire, a location in the United Kingdom
• More, a 2004 one-woman Off-Broadway show by Yeardley Smith

See also[link]

• All pages beginning with "More"
• All pages with titles containing "More"
• More, More, More (disambiguation)
• Moar (disambiguation)
• Mohr (disambiguation)
• Moor (disambiguation)
• Moore (disambiguation)
• Moren (disambiguation)
• Moores (disambiguation)
• Mór (disambiguation)
• MOR (disambiguation)

This disambiguation page lists articles associated with the same title. If an internal link led you here, you may wish to change the link to point directly to the intended article.

This article contains instructions, advice, or how-to content. The purpose of Wikipedia is to present facts, not to train. Please help improve this article either by rewriting the how-to content or by moving it to Wikiversity or Wikibooks. (July 2011)

Text file created with gedit and viewed with a hex editor
Besides the text objects there are only EOL markers
with the hexadecimal value 0A.

In computing, a newline,^[1] also known as a line break or end-of-line (EOL) marker, is a special character or sequence of characters signifying the end of a line of text. The name comes from the fact that the next character after the newline will appear on a new line—that is, on the next line below the text immediately preceding the newline. The actual codes representing a newline vary across operating systems, which can be a problem when exchanging text files between systems with different newline representations.

There is also some confusion whether newlines terminate or separate lines. If a newline is considered a separator, there will be no newline after the last line of a file. The general convention on most systems is to add a newline even after the last line, i.e. to treat newline as a line terminator. Some programs have problems processing the last line of a file if it is not newline terminated. Conversely, programs that expect newline to be used as a separator will interpret a final newline as starting a new (empty) line.

In text intended primarily to be read by humans using software which implements the word wrap feature, a newline character typically only needs to be stored if a line break is required independent of whether the next word would fit on the same line, such as between paragraphs and in vertical lists. See hard return and soft return.

Representations[link]

Software applications and operating systems usually represent a newline with one or two control characters:

• Systems based on ASCII or a compatible character set use either LF (Line feed, '\n', 0x0A, 10 in decimal) or CR (Carriage return, '\r', 0x0D, 13 in decimal) individually, or CR followed by LF (CR+LF, '\r\n', 0x0D0A). These characters are based on printer commands: The line feed indicated that one line of paper should feed out of the printer thus instructed the printer to advance the paper one line, and a carriage return indicated that the printer carriage should return to the beginning of the current line. Some rare systems, such as QNX before version 4, used the ASCII RS (record separator, 0x1E, 30 in decimal) character as the newline character.
  • LF:    Multics, Unix and Unix-like systems (GNU/Linux, Mac OS X, FreeBSD, AIX, Xenix, etc.), BeOS, Amiga, RISC OS and others.
  • CR+LF: Microsoft Windows, DEC TOPS-10, RT-11 and most other early non-Unix and non-IBM OSes, CP/M, MP/M, DOS (MS-DOS, PC-DOS, etc.), Atari TOS, OS/2, Symbian OS, Palm OS
  • LF+CR: Acorn BBC and RISC OS spooled text output.
  • CR:    Commodore 8-bit machines, Acorn BBC, TRS-80, Apple II family, Mac OS up to version 9 and OS-9
  • RS:    QNX pre-POSIX implementation.
• EBCDIC systems—mainly IBM mainframe systems, including z/OS (OS/390) and i5/OS (OS/400)—use NEL (Next Line, 0x15) as the newline character. Note that EBCDIC also has control characters called CR and LF, but the numerical value of LF (0x25) differs from the one used by ASCII (0x0A). Additionally, there are some EBCDIC variants that also use NEL but assign a different numeric code to the character.
• Operating systems for the CDC 6000 series defined a newline as two or more zero-valued six-bit characters at the end of a 60-bit word. Some configurations also defined a zero-valued character as a colon character, with the result that multiple colons could be interpreted as a newline depending on position.
• ZX80 and ZX81, home computers from Sinclair Research Ltd used a specific non-ASCII character set with code NEWLINE (0x76, 118 decimal) as the newline character.
• OpenVMS uses a record-based file system, which stores text files as one record per line. In most file formats, no line terminators are actually stored, but the Record Management Services facility can transparently add a terminator to each line when it is retrieved by an application. The records themselves could contain the same line terminator characters, which could either be considered a feature or a nuisance depending on the application.
• Fixed line length was used by some early mainframe operating systems. In such a system, an implicit end-of-line was assumed every 80 characters, for example. No newline character was stored. If a file was imported from the outside world, lines shorter than the line length had to be padded with spaces, while lines longer than the line length had to be truncated. This mimicked the use of punched cards, on which each line was stored on a separate card, usually with 80 columns on each card. Many of these systems added an carriage control character to the start of the next record, this could indicate if the next record was a continuation of the line started by the previous record, or a new line, or should overprint the previous line (similar to a CR). Often this was a normal printing character such as '#' that thus could not be used as the first character in a line. Some early line printers interpreted these characters directly in the records sent to them.

Most textual Internet protocols (including HTTP, SMTP, FTP, IRC and many others) mandate the use of ASCII CR+LF (0x0D 0x0A) on the protocol level, but recommend that tolerant applications recognize lone LF as well. In practice, there are many applications that erroneously use the C newline character '\n' instead (see section Newline in programming languages below). This leads to problems when trying to communicate with systems adhering to a stricter interpretation of the standards; one such system is the qmail MTA that actively refuses to accept messages from systems that send bare LF instead of the required CR+LF.^[2]

FTP has a feature to transform newlines between CR+LF and LF only when transferring text files. This must not be used on binary files. Usually binary files and text files are recognised by checking their filename extension.

Unicode[link]

The Unicode standard defines a large number of characters that conforming applications should recognize as line terminators:^[3]

 LF:    Line Feed, U+000A
 VT:    Vertical Tab, U+000B
 FF:    Form Feed, U+000C
 CR:    Carriage Return, U+000D
 CR+LF: CR (U+000D) followed by LF (U+000A)
 NEL:   Next Line, U+0085
 LS:    Line Separator, U+2028
 PS:    Paragraph Separator, U+2029

This may seem overly complicated compared to an approach such as converting all line terminators to a single character, for example LF. However, Unicode was designed to preserve all information when converting a text file from any existing encoding to Unicode and back. Therefore, Unicode should contain characters included in existing encodings. NEL is included in ISO-8859-1^{[citation needed]} and EBCDIC (0x15). The approach taken in the Unicode standard allows round-trip transformation to be information-preserving while still enabling applications to recognize all possible types of line terminators.

Recognizing and using the newline codes greater than 0x7F is not often done. They are multiple bytes in UTF-8 and the code for NEL has been used as the ellipsis ('…') character in Windows-1252. For instance:

• YAML^[4] no longer recognizes them as special in order to be compatible with JSON.
• ECMAScript^[5] accepts LS and PS as line breaks, but considers U+0085 (NEL) white space, not a line break.
• Microsoft Windows 2000 does not treat any of NEL, LS or PS as line-break in the default text editor Notepad
• In Linux, a popular editor "gedit" treats LS and PS as newlines but does not for NEL.

History[link]

ASCII was developed simultaneously by the ISO and the ASA, the predecessor organization to ANSI. During the period of 1963–1968, the ISO draft standards supported the use of either CR+LF or LF alone as a newline, while the ASA drafts supported only CR+LF.

The sequence CR+LF was in common use on many early computer systems that had adopted Teletype machines, typically a Teletype Model 33 ASR, as a console device, because this sequence was required to position those printers at the start of a new line. On these systems, text was often routinely composed to be compatible with these printers, since the concept of device drivers hiding such hardware details from the application was not yet well developed; applications had to talk directly to the Teletype machine and follow its conventions.

Most minicomputer systems from DEC used this convention. CP/M used it as well, to print on the same terminals that minicomputers used. From there MS-DOS (1981) adopted CP/M's CR+LF in order to be compatible, and this convention was inherited by Microsoft's later Windows operating system.

The separation of the two functions concealed the fact that the print head could not return from the far right to the beginning of the next line in one-character time. That is why the sequence was always sent with the CR first. In fact, it was often necessary to send extra characters (extraneous CRs or NULs, which are ignored) to give the print head time to move to the left margin. Even many early video displays required multiple character times to scroll the display.

The Multics operating system began development in 1964 and used LF alone as its newline. Multics used a device driver to translate this character to whatever sequence a printer needed (including extra padding characters), and the single byte was much more convenient for programming. The seemingly more obvious choice of CR was not used, as a plain CR provided the useful function of overprinting one line with another, and thus it was useful to not translate it. Unix followed the Multics practice, and later systems followed Unix.

In programming languages[link]

To facilitate the creation of portable programs, programming languages provide some abstractions to deal with the different types of newline sequences used in different environments.

The C programming language provides the escape sequences '\n' (newline) and '\r' (carriage return). However, these are not required to be equivalent to the ASCII LF and CR control characters. The C standard only guarantees two things:

1. Each of these escape sequences maps to a unique implementation-defined number that can be stored in a single char value.
2. When writing a file in text mode, '\n' is transparently translated to the native newline sequence used by the system, which may be longer than one character. When reading in text mode, the native newline sequence is translated back to '\n'. In binary mode, no translation is performed, and the internal representation produced by '\n' is output directly.

On Unix platforms, where C originated, the native newline sequence is ASCII LF (0x0A), so '\n' was simply defined to be that value. With the internal and external representation being identical, the translation performed in text mode is a no-op, and text mode and binary mode behave the same. This has caused many programmers who developed their software on Unix systems simply to ignore the distinction completely, resulting in code that is not portable to different platforms.

The C library function fgets() is best avoided in binary mode because any file not written with the UNIX newline convention will be misread. Also, in text mode, any file not written with the system's native newline sequence (such as a file created on a UNIX system, then copied to a Windows system) will be misread as well.

Another common problem is the use of '\n' when communicating using an Internet protocol that mandates the use of ASCII CR+LF for ending lines. Writing '\n' to a text mode stream works correctly on Windows systems, but produces only LF on Unix, and something completely different on more exotic systems. Using "\r\n" in binary mode is slightly better.

Many languages, such as C++, Perl,^[6] and Haskell provide the same interpretation of '\n' as C.

Java, PHP,^[7] and Python^[8] provide the '\r\n' sequence (for ASCII CR+LF). In contrast to C, these are guaranteed to represent the values U+000A and U+000D, respectively.

The Java I/O libraries do not transparently translate these into platform-dependent newline sequences on input or output. Instead, they provide functions for writing a full line that automatically add the native newline sequence, and functions for reading lines that accept any of CR, LF, or CR+LF as a line terminator (see BufferedReader.readLine()). The System.getProperty() method can be used to retrieve the underlying line separator.

Example:

  String eol = System.getProperty( "line.separator" );
  String lineColor = "Color: Red" + eol;

Python permits "Universal Newline Support" when opening a file for reading, when importing modules, and when executing a file.^[9]

Some languages have created special variables, constants, and subroutines to facilitate newlines during program execution.

Common problems[link]

The different newline conventions often cause text files that have been transferred between systems of different types to be displayed incorrectly. For example, files originating on Unix or Apple Macintosh systems may appear as a single long line on some Windows programs. Conversely, when viewing a file originating from a Windows computer on a Unix system, the extra CR may be displayed as ^M at the end of each line or as a second line break.

The problem can be hard to spot if some programs handle the foreign newlines properly while others do not. For example, a compiler may fail with obscure syntax errors even though the source file looks correct when displayed on the console or in an editor. On a Unix system, the command cat -v myfile.txt will send the file to stdout (normally the terminal) and make the ^M visible, which can be useful for debugging. Modern text editors generally recognize all flavours of CR / LF newlines and allow the user to convert between the different standards. Web browsers are usually also capable of displaying text files and websites which use different types of newlines.

The File Transfer Protocol can automatically convert newlines in files being transferred between systems with different newline representations when the transfer is done in "ASCII mode". However, transferring binary files in this mode usually has disastrous results: Any occurrence of the newline byte sequence—which does not have line terminator semantics in this context, but is just part of a normal sequence of bytes—will be translated to whatever newline representation the other system uses, effectively corrupting the file. FTP clients often employ some heuristics (for example, inspection of filename extensions) to automatically select either binary or ASCII mode, but in the end it is up to the user to make sure his or her files are transferred in the correct mode. If there is any doubt as to the correct mode, binary mode should be used, as then no files will be altered by FTP, though they may display incorrectly.

Conversion utilities[link]

This article contains instructions, advice, or how-to content. The purpose of Wikipedia is to present facts, not to train. Please help improve this article either by rewriting the how-to content or by moving it to Wikiversity or Wikibooks. (June 2010)

Text editors are often used for converting a text file between different newline formats; most modern editors can read and write files using at least the different ASCII CR/LF conventions. The standard Windows editor Notepad is not one of them (although Wordpad and the MS-DOS Editor are).

Editors are often unsuitable for converting larger files. For larger files (on Windows NT/2000/XP) the following command is often used:

TYPE unix_file | FIND "" /V > dos_file

On many Unix systems, the dos2unix (sometimes named fromdos or d2u) and unix2dos (sometimes named todos or u2d) utilities are used to translate between ASCII CR+LF (DOS/Windows) and LF (Unix) newlines. Different versions of these commands vary slightly in their syntax. However, the tr command is available on virtually every Unix-like system and is used to perform arbitrary replacement operations on single characters. A DOS/Windows text file can be converted to Unix format by simply removing all ASCII CR characters with

tr -d '\r' < inputfile > outputfile

or, if the text has only CR newlines, by converting all CR newlines to LF with

tr '\r' '\n' < inputfile > outputfile

The same tasks are sometimes performed with awk, sed, Tr_(Unix) or in Perl if the platform has a Perl interpreter:

awk '{sub("$","\r\n"); printf("%s",$0);}' inputfile > outputfile  # UNIX to DOS  (adding CRs on Linux and BSD based OS that haven't GNU extensions)
awk '{gsub("\r",""); print;}' inputfile > outputfile              # DOS to UNIX  (removing CRs on Linux and BSD based OS that haven't GNU extensions)
sed -e 's/$/\r/' inputfile > outputfile              # UNIX to DOS  (adding CRs on Linux based OS that use GNU extensions)
sed -e 's/\r$//' inputfile > outputfile              # DOS  to UNIX (removing CRs on Linux based OS that use GNU extensions)
cat inputfile | tr -d "\r" > outputfile              # DOS  to UNIX (removing CRs using tr(1). Not Unicode compliant.)
perl -pe 's/\r?\n|\r/\r\n/g' inputfile > outputfile  # Convert to DOS
perl -pe 's/\r?\n|\r/\n/g'   inputfile > outputfile  # Convert to UNIX
perl -pe 's/\r?\n|\r/\r/g'   inputfile > outputfile  # Convert to old Mac

To identify what type of line breaks a text file contains, the file command can be used. Moreover, the editor Vim can be convenient to make a file compatible with the Windows notepad text editor. For example:

[prompt] > file myfile.txt
myfile.txt: ASCII English text
[prompt] > vim myfile.txt
  within vim :set fileformat=dos
             :wq
[prompt] > file myfile.txt
myfile.txt: ASCII English text, with CRLF line terminators

The following grep commands echo the filename (in this case myfile.txt) to the command line if the file is of the specified style:

grep -PL $'\r\n' myfile.txt # show UNIX style file (LF terminated)
grep -Pl $'\r\n' myfile.txt # show DOS style file (CRLF terminated)

For Debian-based systems, these commands are used:

egrep -L $'\r\n' myfile.txt # show UNIX style file (LF terminated)
egrep -l $'\r\n' myfile.txt # show DOS style file (CRLF terminated)

The above grep commands work under Unix systems or in Cygwin under Windows. Note that these commands make some assumptions about the kinds of files that exist on the system (specifically it's assuming only UNIX and DOS-style files—no Mac OS 9-style files).

This technique is often combined with find to list files recursively. For instance, the following command checks all "regular files" (e.g. it will exclude directories, symbolic links, etc.) to find all UNIX-style files in a directory tree, starting from the current directory (.), and saves the results in file unix_files.txt, overwriting it if the file already exists:

find . -type f -exec grep -PL '\r\n' {} \; > unix_files.txt

This example will find C files and convert them to LF style line endings:

find -name '*.[ch]' -exec fromdos {} \;

The file command also detects the type of EOL used:

file myfile.txt
> myfile.txt: ASCII text, with CRLF line terminators

Other tools permit the user to visualise the EOL characters:

od -a myfile.txt
cat -e myfile.txt
hexdump -c myfile.txt

dos2unix, unix2dos, mac2unix, unix2mac, mac2dos, dos2mac can perform conversions. The flip^[10] command is often used.

See also[link]

• ASA carriage control characters
• C0 and C1 control codes
• Page break
• Line starve

References[link]

External links[link]

• The Unicode reference, see paragraph 5.8 in Chapter 5 of the Unicode 4.0 standard (PDF)
• "The End-of-Line Story"
• The [NEL] Newline Character
• The End of Line Puzzle
• Tofrodos - software for Unix that converts to and from DOS newlines
• ToFroWin: a Windows shell extension that is able to convert multiple files from DOS to UNIX (and vice-versa) line endings right from the context menu.
• "Understanding Newlines" on O'Reilly-Net - an article by Xavier Noria.

Wayne LaPierre
Wayne LaPierre in February 2011.
Born	(1948-11-08)November 8, 1948
Education	BA in Education, MA in Government
Alma mater	Siena College, Boston College
Occupation	CEO and Executive Vice President of the NRA, author, television host
Known for	Second Amendment Activism
Home town	Roanoke, VA

Wayne LaPierre (born November 8, 1948),^[1] is an American author and Second Amendment advocate. He is best known for his position as the Executive Vice President of the National Rifle Association.

Background[link]

LaPierre graduated from Patrick Henry High School in Roanoke, VA in 1967. He received his BA in Education from Siena College in Loudonville, NY and his MA in Government from Boston College. He has been a government activist and lobbyist ever since finishing his MA, including positions on the Board of Directors of the American Association of Political Consultants, the American Conservative Union, and the National Fish and Wildlife Foundation.

National Rifle Association Activity[link]

Since 1991, he has served as Executive Vice President and Chief Executive Officer of the National Rifle Association, the largest American gun rights organization. LaPierre joined the NRA in 1977 after working as a legislative aide to a Democratic Virginia Delegate Vic Thomas.

LaPierre has authored several books on weaponry topics, ranging from shooting practices to terrorism to gun safety to crime. He also makes appearances promoting the NRA at gun shows and political events. Citing Democratic candidate John Kerry's history of authoring and supporting gun control legislation, LaPierre actively campaigned against the senator in the 2004 Presidential elections.

In the media[link]

Television[link]

LaPierre hosts Crime Strike, a syndicated weekly television program which advocates gun use for the purpose of self-defense and highlights situations where people have used their guns against criminal suspects.

Online[link]

In October 2006, LaPierre instituted a weekly podcasts on the NRAnews.com website called "What They Didn't Tell You Today." Every weekday, LaPierre gives a short broadcast about gun rights.

Books[link]

• Guns, Crime, and Freedom (1994)
• Shooting Straight: Telling the Truth About Guns in America (2002)
• Guns, Freedom, and Terrorism (2003)
• The Global War on Your Guns (2006)
• The Essential Second Amendment Guide (2007)

Politics[link]

In 2000, LaPierre said President Bill Clinton tolerated a certain amount of violence and killing to strengthen the case for gun control and to score points for his party.^[2] Clinton White House spokesman Joe Lockhart called it "really sick rhetoric, and it should be repudiated by anyone who hears it."^[3]

In 2004, LaPierre debated Rebecca Peters, head of the International Action Network on Small Arms, at King's College London.

References[link]

External links[link]

• NRA Leaders: Wayne LaPierre
• NRAnews.com
• Edited transcript of Rebecca Peters' debate with Wayne LaPierre
• Ruby Ridge documents at TruTV (formerly CourtTV)

This biographical article needs additional citations for verification. Please help by adding reliable sources. Contentious material about living persons that is unsourced or poorly sourced must be removed immediately, especially if potentially libelous or harmful. (October 2011)

Hamid Mohammed Khan is a Socio-Political figure of Telangana^[1] and the President of Movement for Peace and Justice, Andhra Pradesh. He is considered to be the first revolutionary Muslim leader of Telangana Movement^[2].

He is also a leader of Jamaat-e-Islami Hind, Andhra Pradesh and was the Zonal President of Students Islamic Organisation of India, Andhra Pradesh.

See also[link]

Malik Motasim Khan

References[link]

This Indian biographical article is a stub. You can help Wikipedia by expanding it. v t e

Part of a series on Buddhism
History Buddhism History of Buddhism Timeline Councils Gautama Buddha Later Buddhists Category: Buddhism
Teachings concepts Dharma Four Noble Truths Five Aggregates Impermanence Suffering Non-self Dependent Origination Middle Way Emptiness Karma Rebirth Samsara Cosmology Category: Buddhist terms
Practices Threefold Training Three Jewels Noble Eightfold Path Morality Meditation Wisdom Perfections Mindfulness Compassion Aids to Enlightenment Monasticism Laity
Nirvana Nirvāṇa Four Stages Arahant Buddha Bodhisattva
Traditions Schools of Buddhism Hinayana Theravāda Mahāyāna Vajrayāna Tibetan
Texts Buddhist texts Pali Canon Chinese Buddhist canon
Buddhism by country General Countries India India Southern Transmission Sri Lanka Thailand Cambodia Laos Burma Eastern Transmission China Japan Korea Vietnam Indonesia Malaysia Singapore Northern Transmission Tibet Bhutan Mongolia Nepal Russia Western Transmission Western countries USA
Outline Buddhism portal view talk edit

David Robert Loy (born 1947) is an American author and authorized teacher in the Sanbo Kyodan lineage of Japanese Zen Buddhism.^[1][2]

Early life[link]

Loy was born in the Panama Canal Zone. His father was in the U.S. Navy so the family traveled a great deal. He attended Carleton College in Minnesota, and spent his junior year abroad studying philosophy at King’s College, University of London. After graduation in 1969 he moved to San Francisco and then to Hawaii where he began to practice Zen Buddhism.^[1]

Career[link]

Loy received an M.A. in Asian philosophy from the University of Hawaii in 1975, and his Ph.D. in philosophy in 1984 from the National University of Singapore, where he was teaching.^[3] In 1984 Loy moved to Kamakura, Japan to continue Zen practice with Yamada Koun Roshi, director of the Sanbo Kyodan. He was professor of philosophy and religion at Bunkyo University in Chigasaki, Japan until January 2006, when he accepted the Besl Family Chair of Ethics/Religion & Society, a visiting appointment with Xavier University in Cincinnati, Ohio that ended in September 2010.^[3] In 1971, he began practicing Zen with Yamada Koun Roshi and Robert Aitken in Hawaii. He completed formal koan study in 1988 with Yamada Koun and received the dharma name Tetsu-un, "Wisdom Cloud".^[3] Loy's main research interest is the dialogue between Buddhism and modernity, especially the social implications of Buddhist teachings. In addition to academic lectures, he offers workshops and leads meditation retreats in the U.S. and internationally.

In addition to many scholarly papers and popular articles, Loy is the author of several books on comparative philosophy and social ethics, including:

• Nonduality: A Study in Comparative Philosophy (New Haven, Conn: Yale University Press, 1988). A softcover edition was published by Humanities Press in 1997. A German language edition (translation by Clemens Wilhelm) was published as Nondualität: Über die Natur der Wirklichkeit by Krüger, Frankfurt, in 1998. A Spanish language edition (translation by Fernando Mora and David Gonzalez Raga) was published as No dualidad by Kairos Press in 2000. Reviewed by Robert Zeuschner^[4] and by Karl H. Potter.^[5]
• Lack and Transcendence: The Problem of Death and Life in Psychotherapy, Existentialism, and Buddhism (Atlantic Highlands, New Jersey: Humanities Press, 1996). Awarded the 1999 Frederick J. Streng Book Prize by the Society for Buddhist-Christian Studies, for best book of the year. A softcover edition was published by Humanity Books (an imprint of Prometheus Press) in 2000. (review review 2)
• A Buddhist History of the West: Studies in Lack (SUNY Press, 2002).
• The Great Awakening: A Buddhist Social Theory (Boston: Wisdom Publications, 2003). A Spanish language edition (translation by Vicente Merlo) was published as El Gran Despertar: Una teoria social budista by Kairos Press in 2004. A Czech translation was published as Velke Probuzeni by Eugenia Press in 2006.
• The Dharma of Dragons and Daemons: Buddhist Themes in Modern Fantasy (Boston: Wisdom Publications, 2004). Co-authored with his wife Linda Goodhew. Finalist for the 2006 Mythopoeic Scholarship Award in Myth and Fantasy Studies.
• Money, Sex, War, Karma: Notes for a Buddhist Revolution (Wisdom Publications, 2008). Translated and published in Spanish, Italian, French and Dutch.
• Awareness Bound and Unbound: Buddhist Essays (SUNY Press, 2009).
• The World Is Made of Stories (Wisdom Publications, 2010).

Nonduality focuses on the nonduality of subject and object in Buddhism, Vedanta, and Taoism, with reference to several Western thinkers including Wittgenstein and Heidegger. The main argument is that these three Asian systems may be different attempts to describe the same (or very similar) experience. The categories of Buddhism (no self, impermanence, causality, eightfold path) and Advaita Vedanta (all-Self, time and causality as maya, no path) are “mirror images” of each other. Ultimately it becomes difficult to distinguish a formless Being (Brahman) from a formless nonbeing (shunyata). Buddhism can be understood as a more phenomenological description of nonduality, while Vedanta is a more metaphysical account.

Lack and Transcendence: The Problem of Death and Life in Psychotherapy, Existentialism, and Buddhism brings the three traditions together in a synthesis receptive to the insights of each regarding the fundamental issues of life and death and death-in-life. The Buddhist denial of a substantial self implies that our basic problem is not fear of death but fear that we don’t really exist. In response, we become obsessed with “reality projects” (compare Becker’s “immortality projects”) that often make things worse. Later chapters explore the philosophical and psychological implications.

A Buddhist History of the West is not a history of Buddhism in the West but a Buddhist perspective on the development of Western civilization. The Buddhist claim that the (sense of) self is haunted by a (sense of) lack has important historical implications, affecting the ways that (for example) freedom, progress, science, economic and political development have been understood and pursued.

The Great Awakening: A Buddhist Social Theory develops the social implications of Buddhist teachings for our understanding (and response to) collective forms of dukkha (suffering). Today the “three poisons” – greed, ill will, and delusion – have been institutionalized. There are discussions of poverty, economic development, and corporate capitalism; Buddhist perspectives on the war on terror, our criminal justice system, and the connection between Zen and war; and essays addressing technology, deep ecology, and our relationship with the biosphere.

The Dharma of Dragons and Daemons: Buddhist Themes in Modern Fantasy examines the ways that spiritual themes (for example, good and evil, sin and redemption, friendship, time, war and violence, creativity, the meaning of life, the meaning of death) are treated in some of the classics of contemporary fantasy: The Lord of the Rings, Ende’s Momo, the anime of Hayao Miyazaki, Pullman’s His Dark Materials, and Le Guin’s Earthsea.

Money, Sex, War, Karma: Notes for a Buddhist Revolution is a series of short essays that begins with the essential teaching of the Buddha: the connection between suffering and the delusive (sense of) self, usually experienced as a sense of lack. Subsequent essays discuss the implications for the ways we understand money, fame, karma, food, sexuality and romantic love, consumerism, ecology, war, and social engagement.

Awareness Bound and Unbound: Buddhist Essays is a collection of related essays on Buddhist and comparative issues, including language, truth and deconstruction; Taoism, Christianity (Swedenborg, The Cloud of Unknowing), and postmodernism; the karma of women; violence, the clash of civilizations, and the war on terror.

The World Is Made of Stories is a sequence of “micro-essays” and quotations that offer a new way of understanding Buddhism and a new Buddhist understanding of the Way, consistent with what Buddhism says about the human predicament and how it can be resolved. If the self is composed of the stories one identifies with and attempts to live, karma is not what the self has but what the sense of self becomes, as we play habitual roles within stories perceived as objectively real.

Loy is also the editor of Healing Deconstruction: Postmodern Thought in Buddhism and Christianity (Atlanta, GA: Scholars Press, 1996), with essays by Roger Corless, Philippa Berry, Morny Joy, Robert Magliola, and David Loy; and the co-editor (with John Stanley and Gyurme Dorje) of A Buddhist Response to the Climate Emergency (Wisdom Publications, 2009), which includes contributions by the Dalai Lama, Thich Nhat Hanh, the Karmapa, Robert Aitken, Joanna Macy, Bhikkhu Bodhi, Joseph Goldstein, Matthieu Ricard, Lin Jensen, and many others.

Loy appears in the 2003 documentary Flight From Death, a film that investigates the relationship of human violence to fear of death, as related to subconscious influences.

He sits on the editorial or advisory boards of the journals Cultural Dynamics, Worldviews, Contemporary Buddhism, Journal of Transpersonal Psychology, and World Fellowship of Buddhists Review.

Personal life[link]

He is married to Linda Goodhew, formerly an associate professor of English literature at Gakushuin University in Tokyo, Japan. They have one son, Mark Loy Goodhew.

References[link]

This Zen-related article is a stub. You can help Wikipedia by expanding it. v t e