Sponsored Content
Full Discussion: .bashrc in Ubuntu 14.04
Operating Systems Linux Fedora .bashrc in Ubuntu 14.04 Post 302955798 by cmccabe on Monday 21st of September 2015 04:28:41 PM
Old 09-21-2015
How can I remove this if I can not access nano? Is there a command? Thank you Smilie.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

from bashrc to sh..??

:) as soon as i installed my software a couple of weeks ago.. (fedora core 2 vs, 2.6.8-1.521) i decided to switch the shell to sh shell and i know that .bashrc is the bash profile file(???) i want to use the sh version of the same file and make it the main profile file.. how can I switch it and... (3 Replies)
Discussion started by: moxxx68
3 Replies

2. UNIX for Dummies Questions & Answers

history -c in my .bashrc

Hi, I come into unix with csh, but i switch to bash . I want to clear my command history for each session, history -c, but for some reason this doesn't work in the .bashrc file. I know that the file is running after I type bash on my csh command line because I get the hello back. If I am already... (1 Reply)
Discussion started by: yankee428
1 Replies

3. UNIX for Dummies Questions & Answers

Having trouble with .bashrc

hey guys, Im trying to find all my .bashrc files in the home directory. ~/etc/bash.bashrc is the only thing i can find but its outside of my /home Could the files be hidden? I want to see all my .bashrc files in my /home structure... <cries> (5 Replies)
Discussion started by: oxoxo
5 Replies

4. UNIX for Dummies Questions & Answers

.bashrc question

Hi, I was instructed to find all the .bashrc files on my system, that MODIFY the PS1 varaible. here is what i've come up with so far: ls / .bashrc -print woo. But thats not all. I need to display the full file name ( Including the full path ) and protection. - I can display... (4 Replies)
Discussion started by: oxoxo
4 Replies

5. UNIX for Dummies Questions & Answers

.bashrc revisisted

hey guys, i've tried countless times to do this and have come up with: find / type -f ".bashrc" -exec grep PS1 '{}' \; 2>/dev/null | ls -l which tells bash: find all the files in the system with the name .bashrc and look for modifcations to PS1 and terminate and rediret error msgs... (8 Replies)
Discussion started by: oxoxo
8 Replies

6. Shell Programming and Scripting

bashrc

i have made a few changes to my bashrc file...have set a few environmental variable that my shell scripts use. Is there any way that these changes can reflect in evryone else's bashrc who are in the network or do all of them have to copy those changes to their own bashrc file. (2 Replies)
Discussion started by: lassimanji
2 Replies

7. Shell Programming and Scripting

bashrc not saving changes

I am trying to do some changes at bashrc file located at /etc directory of my server. First I tried to edit bashrc via FTP downloaded on my pc changed it and loaded back, but it seems like changes are not reflecting. Therefore I tried to change it via putty shel using vim bashrc command. but... (4 Replies)
Discussion started by: ninadgac
4 Replies

8. UNIX for Advanced & Expert Users

unset .bashrc

Could someone please tell me how to unset your .bashrc? I have tried all of these. I can't find anything useful from google. unset -f .bashrc unset .bashrc (9 Replies)
Discussion started by: cokedude
9 Replies

9. Shell Programming and Scripting

Modifying the .bashrc

I have modified the .bashrc. The problem is that when I write a long command, it does not write on the next line but continues to write on the same line. # ~/.bashrc: executed by bash(1) for non-login shells. # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) # for... (1 Reply)
Discussion started by: kristinu
1 Replies

10. UNIX for Advanced & Expert Users

.bashrc questions

Are there any advantages of doing one over the other in your .bashrc? They both seem to do the same thing. HISTFILESIZE=10000 HISTSIZE=10000export HISTFILESIZE=10000 export HISTSIZE=10000 (4 Replies)
Discussion started by: cokedude
4 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 09:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy