Sponsored Content
Full Discussion: Wordpad or Notepad?
Special Forums UNIX Desktop Questions & Answers Wordpad or Notepad? Post 302318339 by SilversleevesX on Thursday 21st of May 2009 10:40:31 AM
Old 05-21-2009
If you'd rather stay in the Windows GUI for your scripts in the log run...

... there are two options, and they're both freeware.

* Crimson Editor, which is so great for creating, editing and saving Unix files that I now have it set to edit practically every .dot file in my Cygwin install.

* Alpine, a standalone version of Pine (Unix email client) and Pico (text editor) paired by their authors and onetime maintainers at the University of Washington. The Pico standalone app saves in UTF-8, so it might be worthwhile checking some of its saved output via cat or vi before uploading any of it. I'm partial to Pico and nano anyway, so I was very gratified to find there was a Win32 standalone of the former.

Quote:
Originally Posted by JustIce
regardless of what text editor one uses in windows, one should always get proficient in vi at a minimum --- ed would be even better ---
Here I would have to agree. Even the OS X Terminal, while providing nano (and maybe pico too, nowadays, who knows), installs with vim (vi modified) as the $EDITOR selection in its .bashrc. And most of the helps and how-to's for Mac command-line you find on the Web assume you use vim as your editor.

Hope this was helpful.

BZT

Quote:
Originally Posted by Heidi.Ebbs
Being new to UNIX, using the editor VI has previously proved to be a bit of a challenge and has taken some time to come to terms with the different keys that should be used for navigating around VI.

However, since posting this topic I have been on a UNIX course and have a much better understanding now of permissions, FTP, VI and much more

:-)

Last edited by SilversleevesX; 05-21-2009 at 11:56 AM.. Reason: Pointed up the difference between CLI and S/A Pico
 

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Strange Characters After Using Notepad

Hello all, I'm new to UNIX and new to this forum, so forgive my lack of knowledge. I'm new with editing in vi so I FTP scripts to a Windows machine and edit the script in notepad (when I need to do something quickly). Sometimes when I FTP the script back to the UNIX box, strange characters... (4 Replies)
Discussion started by: dgower2
4 Replies

2. UNIX for Dummies Questions & Answers

Output of the script in notepad

Hi All, I want to show my output for the script to notepad.Anybody know what is the command to do this... Thanks.. (7 Replies)
Discussion started by: mastercar
7 Replies

3. Solaris

Wordpad file in solaris

i have a file which i open in wordpad shows proper formated o/p column wise .. but same file which is txt file when i do cat in solaris shows grabbled o/p is there any way i can see the output same as wordpad or txt pad ? even in solaris ? Following is the o/o when i do a #cat file.txt | more... (8 Replies)
Discussion started by: fugitive
8 Replies

4. UNIX for Dummies Questions & Answers

Formatting from Notepad++ to Vi

Hi, just quick question, I currently type up my scripts in Notepad++ and then copy them into my file (in VI). However, i've noticed that all the lines get messed up and it becomes difficult to read the script. so i've to spend time then using '\' at the end of lines etc and re-formatting... (7 Replies)
Discussion started by: horhif
7 Replies

5. Windows & DOS: Issues & Discussions

UNIX and notepad++

I connect to my office server using ftp option in notepad++ I am not able to open directory's with out setting my clear case view in the notepad++ Hence pls help me in setting the view in notepad++ so that it can read all the files and directorys (6 Replies)
Discussion started by: Syed Imran
6 Replies
NANO(1) 						      General Commands Manual							   NANO(1)

NAME
nano - Nano's ANOther editor, an enhanced free Pico clone SYNOPSIS
nano [OPTIONS] [[+LINE,COLUMN] FILE]... DESCRIPTION
This manual page briefly documents the nano command. nano is a small, free and friendly editor which aims to replace Pico, the default editor included in the non-free Pine package. Rather than just copying Pico's look and feel, nano also implements some missing (or disabled by default) features in Pico, such as "search and replace" and "go to line and column number". OPTIONS
+LINE,COLUMN Places cursor at line number LINE and column number COLUMN (at least one of which must be specified) on startup, instead of the default of line 1, column 1. -? Same as -h (--help). -A (--smarthome) Make the Home key smarter. When Home is pressed anywhere but at the very beginning of non-whitespace characters on a line, the cur- sor will jump to that beginning (either forwards or backwards). If the cursor is already at that position, it will jump to the true beginning of the line. -B (--backup) When saving a file, back up the previous version of it to the current filename suffixed with a ~. -C dir (--backupdir=dir) Set the directory where nano puts unique backup files if file backups are enabled. -D (--boldtext) Use bold text instead of reverse video text. -E (--tabstospaces) Convert typed tabs to spaces. -F (--multibuffer) Enable multiple file buffers, if available. -H (--historylog) Log search and replace strings to ~/.nano_history, so they can be retrieved in later sessions, if nanorc support is available. -I (--ignorercfiles) Don't look at SYSCONFDIR/nanorc or ~/.nanorc, if nanorc support is available. -K (--rebindkeypad) Interpret the numeric keypad keys so that they all work properly. You should only need to use this option if they don't, as mouse support won't work properly with this option enabled. -L (--nonewlines) Don't add newlines to the ends of files. -N (--noconvert) Disable automatic conversion of files from DOS/Mac format. -O (--morespace) Use the blank line below the titlebar as extra editing space. -Q str (--quotestr=str) Set the quoting string for justifying. The default is "^([ ]*[#:>|}])+" if extended regular expression support is available, or "> " otherwise. Note that stands for a Tab. -R (--restricted) Restricted mode: don't read or write to any file not specified on the command line; read any nanorc files; allow suspending; allow a file to be appended to, prepended to, or saved under a different name if it already has one; or use backup files or spell checking. Also accessible by invoking nano with any name beginning with 'r' (e.g. "rnano"). -S (--smooth) Enable smooth scrolling. Text will scroll line-by-line, instead of the usual chunk-by-chunk behavior. -T cols (--tabsize=cols) Set the size (width) of a tab to cols columns. The value of cols must be greater than 0. The default value is 8. -U (--quickblank) Do quick statusbar blanking. Statusbar messages will disappear after 1 keystroke instead of 25. Note that -c overrides this. -V (--version) Show the current version number and exit. -W (--wordbounds) Detect word boundaries more accurately by treating punctuation characters as part of a word. -Y str (--syntax=str) Specify a specific syntax highlighting from the nanorc to use, if available. -c (--const) Constantly show the cursor position. Note that this overrides -U. -d (--rebinddelete) Interpret the Delete key differently so that both Backspace and Delete work properly. You should only need to use this option if Backspace acts like Delete on your system. -h (--help) Show a summary of command line options and exit. -i (--autoindent) Indent new lines to the previous line's indentation. Useful when editing source code. -k (--cut) Enable cut from cursor to end of line. -l (--nofollow) If the file being edited is a symbolic link, replace the link with a new file instead of following it. Good for editing files in /tmp, perhaps? -m (--mouse) Enable mouse support, if available for your system. When enabled, mouse clicks can be used to place the cursor, set the mark (with a double click), and execute shortcuts. The mouse will work in the X Window System, and on the console when gpm is running. -o dir (--operatingdir=dir) Set operating directory. Makes nano set up something similar to a chroot. -p (--preserve) Preserve the XON and XOFF sequences (^Q and ^S) so they will be caught by the terminal. -r cols (--fill=cols) Wrap lines at column cols. If this value is 0 or less, wrapping will occur at the width of the screen less cols columns, allowing the wrap point to vary along with the width of the screen if the screen is resized. The default value is -8. -s prog (--speller=prog) Enable alternative spell checker command. -t (--tempfile) Always save changed buffer without prompting. Same as Pico's -t option. -v (--view) View file (read only) mode. -w (--nowrap) Disable wrapping of long lines. -x (--nohelp) Disable help screen at bottom of editor. -z (--suspend) Enable suspend ability. -a, -b, -e, -f, -g, -j Ignored, for compatibility with Pico. INITIALIZATION FILE
nano will read initialization files in the following order: SYSCONFDIR/nanorc, then ~/.nanorc. Please see nanorc(5) and the example file nanorc.sample, both of which should be provided with nano. NOTES
If no alternative spell checker command is specified on the command line or in one of the nanorc files, nano will check the SPELL environ- ment variable for one. In some cases nano will try to dump the buffer into an emergency file. This will happen mainly if nano receives a SIGHUP or SIGTERM or runs out of memory. It will write the buffer into a file named nano.save if the buffer didn't have a name already, or will add a ".save" suffix to the current filename. If an emergency file with that name already exists in the current directory, it will add ".save" plus a number (e.g. ".save.1") to the current filename in order to make it unique. In multibuffer mode, nano will write all the open buffers to their respective emergency files. BUGS
Please send any comments or bug reports to nano@nano-editor.org. The nano mailing list is available from nano-devel@gnu.org. To subscribe, email to nano-devel-request@gnu.org with a subject of "subscribe". HOMEPAGE
http://www.nano-editor.org/ SEE ALSO
nanorc(5) /usr/share/doc/nano/ (or equivalent on your system) AUTHOR
Chris Allegretta <chrisa@asty.org>, et al (see AUTHORS and THANKS for details). This manual page was originally written by Jordi Mallach <jordi@gnu.org>, for the Debian system (but may be used by others). October 28, 2006 version 2.0.0 NANO(1)
All times are GMT -4. The time now is 03:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy