vi editor on CYGWIN Post: 302694539

Login or Register to Ask a Question and Join Our Community

Sponsored Content

Top Forums Shell Programming and Scripting vi editor on CYGWIN Post 302694539 by liyakathali on Friday 31st of August 2012 02:30:53 AM

Old

08-31-2012

Registered User

'vi editor on CYGWIN

I tried to create a file using the command vi <filename> on CYGWIN but it is not working.Please help me with the solution.

---------- Post updated at 02:30 AM ---------- Previous update was at 02:29 AM ----------

Quote:

Originally Posted by CarloM

'not working' isn't very descriptive. Details?

I tried to create a file using the command vi <filename> on CYGWIN but it is not working.Please help me with the solution..Please help me with the solution.

liyakathali

View Public Profile for liyakathali

Find all posts by liyakathali

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

E:348 no string under cursor error comes in vi editor in cygwin

when i open a file to edit and type i to insert and the type # for #!/bin/bash in vi and vim editor the message come that no string under cursor plz somebody help

2. UNIX for Dummies Questions & Answers

vi editor in cygwin

I have downloaded latest cygwin editor for windows xp. vi editor is not working on it. the error i get is "vi : command not found" I have already seen a post in this forum regarding the issue but the links in the post are broken. So please help on this issue. thanks in advance

3. UNIX for Dummies Questions & Answers

Pasting text in VI editor from a different editor

Hi, I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question. How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'? As i see, p & P options does work only within 'vi'.

4. Shell Programming and Scripting

set EDITOR=vi -> default editor not setting for cron tab

Hi All, I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by set EDITOR=vi it does not open a vi editor , rather it do as below..... ///////////////////////////////////////////////////// $ set...

5. Solaris

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :Licen

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down

6. UNIX for Dummies Questions & Answers

cygwin vi editor

now i am new to unix... i installed cygwin on windows because i want to make c++ program... and i need vi editor... whenever i write (vi anything) in the cygwin terminal it says vi: command not found ...since i installed all the packages

7. Shell Programming and Scripting

editor mode in cygwin

Hi, I am using CYGWIN for script testing. I have found that vi command does not work in this. Kindly suggest how can I edit a script that is stored in a file ???

8. UNIX for Dummies Questions & Answers

tip: Simple script won't run in cygwin - vim editor involved

I ran into this issue and thanks to various postings in various forums, was able to figure out the solution but didn't see one posting that laid the whole issue out cleanly. So thought the following might help others ... ------------------------------------------------------------------------...

9. Shell Programming and Scripting

vi Editor on Cygwin

I installed Cygwin today and my vi editor was not working i.e. on while using vi command, I was getting "command not found" error. I realized that many have faced this problem and the previous threads on this have been closed without complete answers. I tried something and it worked. Wanted to...

10. Shell Programming and Scripting

opening new instance of cygwin from withing cygwin

I'm using cygwin on win7, What I would like to do is something like this: cygstart cygwin tail -f /foo/test.log | perl -pe 's/error/\e I know I can start a new instance using either of these: mintty -e ... cygstart tail ... But neither of those open in ANSI mode, so I can't do...

LEARN ABOUT OPENDARWIN

end

GET_END(3)						     Library Functions Manual							GET_END(3)

NAME

       get_end, get_etext, get_edata - get values of UNIX link editor defined symbols

SYNOPSIS

       #include <mach-o/getsect.h>

       unsigned long get_end();
       unsigned long get_etext();
       unsigned long get_edata();

DESCRIPTION

       These routines provide a stopgap measure to programs that use the UNIX link-editor defined symbols.  Use of these routines is very strongly
       discouraged.  The problem is that any program that is using UNIX link editor defined symbols (_end, _etext or _edata) is making assumptions
       that the program has the memory layout of a UNIX program.

       This is an incorrect assumption for a program built by the Mach-O link editor.  The reason that these routines are provided is that if very
       minimal assumptions about the layout are used and the default format and memory layout of the Mach-O link editor is used to build the  pro-
       gram,  some things may work by using the values returned by these routines in place of the addresses of their UNIX link-editor defined sym-
       bols.  So use at your own risk, and only if you know what your doing.  Or better yet, convert the program to use the  appropriate  Mach	or
       Mach-O  functions.   If	you  are  trying to allocate memory use vm_allocate(2), if you are trying to find out about your address space use
       vm_region(2) and if you are trying to find out where your program is loaded use the dyld(3) functions.

       The values of the UNIX link-editor defined symbols _etext, _edata and _end are returned by the routines get_etext, get_edata,  and  get_end
       respectively.  In a Mach-O file they have the following values: get_etext returns the first address after the (__TEXT,__text) section, note
       this my or may not be the only section in the __TEXT segment.  get_edata returns the first address after the (__DATA,__data) section,  note
       this  my  or  may not be the last non-zero fill section in the __DATA segment.  get_end returns the first address after the last segment in
       the executable, note a shared library may be loaded at this address.

SEE ALSO

       ld(1), dyld(3)

Apple Computer, Inc.						  April 10, 1998							GET_END(3)