Sponsored Content
Full Discussion: Making any script executable
Top Forums Shell Programming and Scripting Making any script executable Post 302954348 by RavinderSingh13 on Monday 7th of September 2015 06:43:38 AM
Old 09-07-2015
Hello HelenaR,

You could use following steps for same.

To edit a file called filename, type nano filename.
Insert new text(which is I guess
Code:
#!bin/ksh 
chmod +x Input_file

) at the current cursor position just by typing the text in.

^O save contents without exiting (you will be prompted for a file to save to)
^X exit nano (you will be prompted to save your file if you haven't)
^T when saving a file, opens a browser that allows you to select a file name from a list of files and directories.

Hope this helps you.

Thanks,
R. Singh
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

pls hlp: making .sh files executable

I've got a file named jdictd.sh containing the following: --- begin file contents --- #! /bin/csh echo I\'m running! java -cp jdictd.jar org.dict.server.JDictd data/dict.ini # Use the following line instead if JRE 1.1 is used # jre -cp jdictd.jar org.dict.server.JDictd data/dict.ini ---end... (2 Replies)
Discussion started by: ropers
2 Replies

2. AIX

Making Executable File

Hi All: I am a newbie. I have shell script and bunch of java jar files and I want to give one single executable file (may be .bin). Ex: I have test.sh, jar1.jar, jar2.jar. I have to make process.xxx When we run "process.xxx" it will run the "test.sh" script which inturn uses jar1.jar and... (0 Replies)
Discussion started by: laxman123
0 Replies

3. UNIX for Dummies Questions & Answers

Making UNIX script executable

Hello, I am very new to UNIX and I have been learning about writing scripts and making them executable. I created a script called myscript. It has three lines: #! /bin/sh # This is my first shell script echo friendsjustfriends Now I try to run it using the sh command and it works Next I... (4 Replies)
Discussion started by: rohitx
4 Replies

4. UNIX for Dummies Questions & Answers

need help making a script executable

making a script in vi to create a shell script called wherearethey by entering the following script: echo -n "Who are you looking for: "read userif then list=`w | grep $user | cut -c19-30` if then echo "The user $user is logged in from $list" else echo "The user $user is not logged in... (3 Replies)
Discussion started by: curtner
3 Replies

5. Shell Programming and Scripting

problem in making Awk executable script

Guys I placed #!path/awk -f placed awk script and used $1 to call 1st inputfile inside the script. But some where I did mistake. Could you please help me run this script as executable I forgot to mention I also used BEGIN before placing awk script. But nothing worked out. Script ... (2 Replies)
Discussion started by: repinementer
2 Replies

6. UNIX for Dummies Questions & Answers

Making file executable

Hi guys, i'm trying to make a file called 'run-all-tests' executable but it is not letting me for some reason. I am presented with the following error: chmod: cannot access `./run-tests': No such file or directory Basically i have a folder called ex3 and within that there are task folders:... (11 Replies)
Discussion started by: Shyamz1
11 Replies

7. Shell Programming and Scripting

Making a perl script executable

Hello, I have a perl program called snp_hwe.pl I have another program called hwe_test.run which contains the following: for file in *.inp do cp $file genotype_counts_c.txt ./snp_hwe.exe > $file'.res' done I want to change my perl program to an executable program while changing... (3 Replies)
Discussion started by: Homa
3 Replies

8. UNIX for Advanced & Expert Users

What choice when "making" an executable on FreeBSD?

I should make an executable on our server, and are having some problem (I changed this question cause I found out that anser). I'm getting this error when trying to do make: In file included from... /usr/include/sys/file.h:161: error: expected specifier-qualifier-list before 'u_int' *** Error... (1 Reply)
Discussion started by: 244an
1 Replies

9. Shell Programming and Scripting

Making bash script allways executable when transfer ?

Does it possible to make some bash script automatic to be a executable when transfered to another pc...? (5 Replies)
Discussion started by: tomislav91
5 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 05:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy