Sponsored Content
Top Forums UNIX for Advanced & Expert Users line endings help of non-ASCII files Post 302479078 by cokedude on Thursday 9th of December 2010 06:27:15 PM
Old 12-09-2010
For certain things like shellscripts line endings are VERY important. Shellscripts will only work with LF and not CRLF line endings. I'm sure there are other things but that is the only thing I can think of off the top of my head.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ASCII Files

Can you pls help on writing ASCII files? For example, how to you put SUPPLIER NO and NAME in an ASCIIfile? (1 Reply)
Discussion started by: yialousa
1 Replies

2. UNIX for Advanced & Expert Users

create email w/ ASCII attachment via command-line

All, I need to email an ASCII data file to a business partner, and intended on creating a Korn Shell script to create an email message (minimal text), and attach the ASCII data file to the email. It seems this is not as easy as I had thought it might be. sendmail does not support... (3 Replies)
Discussion started by: jwperry
3 Replies

3. Shell Programming and Scripting

New line characters in Ascii file

I am having a file(1234.txt) downloaded from windows server (in Ascii format).However when i ftp this file to Unix server and try to work with it..i am unable to do anything.When i try to open the file using vi editor the file opens in the following format ... @ @ @ @ @ @ @ @... (4 Replies)
Discussion started by: appu2176
4 Replies

4. Shell Programming and Scripting

Problems with Sed/awk/grep and line endings

Hello I have created the following script, which is designed to manipulate a text document: #!/bin/sh # Get 3 lines, (last of which is "Quantity"); adjust order; put all three on one line with tabs. FILENAME=~/Desktop/email.txt LIST=$(grep -B2 "Quantity" ${FILENAME} |awk 'BEGIN { FS = "\n"; RS... (6 Replies)
Discussion started by: benwiggy
6 Replies

5. UNIX for Advanced & Expert Users

Vi line endings conversions

I was reading these 2 articles. Why does the wikia one think :e ++ff=dos? Or am I just misunderstanding it? :e ++ff=unix :e ++ff=dos File format - Vim Tips Wiki Managing/Munging Line-Endings with Vi/Vim | Jeet Sukumaran (1 Reply)
Discussion started by: cokedude
1 Replies

6. UNIX for Dummies Questions & Answers

Find a file that could have different endings

Hello all. Hope you can help. I am looking for a complete command to search for a file named HOSPCHK. The file could be listed with numbers after it like it could be listed with letters after it or a combination of both or just by it self. The other catch is the file that I want to look for... (27 Replies)
Discussion started by: azapp51
27 Replies

7. Red Hat

Installing Generic Ascii Drivers For Line Matrix Printer

Hi, Does anybody have any idea as to how to setup a printer using a generic ascii driver? We have a Tally T6100 line matrix printer which is on our network and works fine in a Windows environment. We are trying to move this printer to Oracle Linux. I've contacted Tally as well as Printronix... (0 Replies)
Discussion started by: garethnsolomons
0 Replies

8. UNIX for Advanced & Expert Users

vimrc help with line endings

I was reading this and thought I could put this in my vimrc and it would convert the line endings to unix. Am I doing something wrong or am I missing something? set ff=unixManaging/Munging Line-Endings with Vi/Vim | Jeet Sukumaran I used this command and it confirms that my global option is... (2 Replies)
Discussion started by: cokedude
2 Replies

9. Shell Programming and Scripting

Sendmail ignoring line endings

Mails from Sendmail are ignoring line endings, when I try to send email with attachment. I have tried to specify the font in the html but line endings are still ignored. I also tried unix2dos, still no luck. #!/usr/bin/ksh ###Send Email MAILTO=`cat mail2.list | tr -s '\n' ','` SUBJECT="bla bla... (3 Replies)
Discussion started by: aydj
3 Replies

10. UNIX for Beginners Questions & Answers

Tip to remove line endings and spaces on a pre-formatted text file?

Hi, At the moment, using Notepad++ to do a search and replace, manually section by section which is real painful. Yeah, so copying each section of the line of text and putting into a file and then search and replace, need at least 3-operations in Notepad++. Here's hoping I will be able to... (1 Reply)
Discussion started by: newbie_01
1 Replies
UNZIP(1)						    BSD General Commands Manual 						  UNZIP(1)

NAME
unzip -- extract files from a ZIP archive SYNOPSIS
unzip [-aCcfjLlnopqtuvy] [-d dir] [-x pattern] zipfile DESCRIPTION
The following options are available: -a When extracting a text file, convert DOS-style line endings to Unix-style line endings. -C Match file names case-insensitively. -c Extract to stdout/screen. When extracting files from the zipfile, they are written to stdout. This is similar to -p, but doesn't suppress normal output. -d dir Extract files into the specified directory rather than the current directory. -f Update existing. Extract only files from the zipfile if a file with the same name already exists on disk and is older than the former. Otherwise, the file is silently skipped. -j Ignore directories stored in the zipfile; instead, extract all files directly into the extraction directory. -L Convert the names of the extracted files and directories to lowercase. -l List, rather than extract, the contents of the zipfile. -n No overwrite. When extracting a file from the zipfile, if a file with the same name already exists on disk, the file is silently skipped. -o Overwrite. When extracting a file from the zipfile, if a file with the same name already exists on disk, the existing file is replaced with the file from the zipfile. -p Extract to stdout. When extracting files from the zipfile, they are written to stdout. The normal output is suppressed as if -q was specified. -q Quiet: print less information while extracting. -t Test: do not extract anything, but verify the checksum of every file in the archive. -u Update. When extracting a file from the zipfile, if a file with the same name already exists on disk, the existing file is replaced with the file from the zipfile if and only if the latter is newer than the former. Otherwise, the file is silently skipped. -v List verbosely, rather than extract, the contents of the zipfile. This differs from -l by using the long listing. Note that most of the data is currently fake and does not reflect the content of the archive. -x pattern Exclude files matching the pattern pattern. -y Print four digit years in listings instead of two. Note that only one of -n, -o, and -u may be specified. ENVIRONMENT
If the UNZIP_DEBUG environment variable is defined, the -q command-line option has no effect, and additional debugging information will be printed to stderr. COMPATIBILITY
The unzip utility aims to be sufficiently compatible with other implementations to serve as a drop-in replacement in the context of the pkgsrc(7) system. No attempt has been made to replicate functionality which is not required for that purpose. For compatibility reasons, command-line options will be recognized if they are listed not only before but also after the name of the zipfile. Normally, the -a option should only affect files which are marked as text files in the zipfile's central directory. Since the archive(3) library reads zipfiles sequentially, and does not use the central directory, that information is not available to the unzip utility. Instead, the unzip utility will assume that a file is a text file if no non-ASCII characters are present within the first block of data decompressed for that file. If non-ASCII characters appear in subsequent blocks of data, a warning will be issued. The unzip utility is only able to process ZIP archives handled by libarchive(3). Depending on the installed version of libarchive(3), this may or may not include self-extracting archives. SEE ALSO
libarchive(3) HISTORY
The unzip utility appeared in NetBSD 6.0. AUTHORS
The unzip utility and this manual page were written by Dag-Erling Smorgrav <des@FreeBSD.org>. It uses the archive(3) library developed by Tim Kientzle <kientzle@FreeBSD.org>. BUGS
The unzip utility currently does not support asking the user whether to overwrite or skip a file that already exists on disk. To be on the safe side, it will fail if it encounters a file that already exists and neither the -n nor the -o command line option was specified. BSD
August 18, 2011 BSD
All times are GMT -4. The time now is 08:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy