Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: What editor does everyone use?
Top Forums Programming Open Source What editor does everyone use? Post 76132 by tmarikle on Friday 24th of June 2005 05:01:46 PM
Old 06-24-2005
more to dangral and google's point: vi seems clumsy at first but once you have taken advantage of vi's considerable functionality once or twice, you won't be saying "I hate it" anymore. In fact, you're going to be quickly downloading a Windoze version. Smilie
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Vi editor ?

Hello everybody, My question is: how to add /tmp/work at the end of line in vi editor. my file looks like: cp file1 cp file2 cp file3 **** I need to add " /tmp/work" at the end of each line. I tried this :%s/$/" /tmp/work" and this :%s/$/\ /tmp/work\/ but it does not work. (2 Replies)
Discussion started by: billy5
2 Replies

2. HP-UX

instead VI editor - which one?

I'd like to find some editor for HP-UX, something like notepad, but not VI editor. Can someone have some ideas which one? thx (6 Replies)
Discussion started by: diamond
6 Replies

3. UNIX for Advanced & Expert Users

vi editor

Hi, how can I add at the begining and at the end of all of the lines of my text file in VI editor ? Many thanks before. for exemple if in my file i have line 1 line 2 I want to have : start line 1 end start line 2 end (3 Replies)
Discussion started by: alain123456
3 Replies

4. UNIX Desktop Questions & Answers

best editor

We work on AIX 5L We use vi as text editor (only scripts to create and modifiy). What do you think of emacs ? Where can I find it ? Do you know better text editor for scripts ? Thank you for all answers. (1 Reply)
Discussion started by: annemar
1 Replies

5. HP-UX

vi editor

I am new in hp ux and I want work with vi editor, but in hp ux vi editor the backspaes and del keys doesn't work. how can I enable them. thanks (3 Replies)
Discussion started by: hkoolivand
3 Replies

6. 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'. (10 Replies)
Discussion started by: harishmitty
10 Replies

7. 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... (6 Replies)
Discussion started by: aarora_98
6 Replies

8. 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 (1 Reply)
Discussion started by: durgaprasadr13
1 Replies

9. Shell Programming and Scripting

About vi editor

How can ` character be printed on vi editor ? empl_id=`echo $line | awk ' { print $1; } '` (2 Replies)
Discussion started by: senem
2 Replies

10. Shell Programming and Scripting

Not able to use @ in VI editor

Hello All, Need one Help for one issue. I am using a French Keyboard, so @ sign is on key 0 and i have to use right Alt + 0 to print it. It is working everywhere but not inside Vi editor. I can type @ in shell, in notepad. But inside Vi editor it is not working, another problem is that if... (2 Replies)
Discussion started by: yadavricky
2 Replies

LEARN ABOUT DEBIAN

go-remote

GO-REMOTE(7)						 Miscellaneous Information Manual					      GO-REMOTE(7)

NAME

       go - tool for managing Go source code

DESCRIPTION

       An  import path (see go-importpath(1)) denotes a package stored in the local file system.  Certain import paths also describe how to obtain
       the source code for the package using a revision control system.

       A few common code hosting sites have special syntax:

       BitBucket (Mercurial)
	      import "bitbucket.org/user/project"
	      import "bitbucket.org/user/project/sub/directory"

       GitHub (Git)
	      import "github.com/user/project"
	      import "github.com/user/project/sub/directory"

       Google Code Project Hosting (Git, Mercurial, Subversion)
	      import "code.google.com/p/project"
	      import "code.google.com/p/project/sub/directory"

	      import "code.google.com/p/project.subrepository"
	      import "code.google.com/p/project.subrepository/sub/directory"

       Launchpad (Bazaar)

	      import "launchpad.net/project"
	      import "launchpad.net/project/series"
	      import "launchpad.net/project/series/sub/directory"

	      import "launchpad.net/~user/project/branch"
	      import "launchpad.net/~user/project/branch/sub/directory"

       For code hosted on other servers, import paths may either be qualified with the version control type, or the go tool can dynamically  fetch
       the import path over https/http and discover where the code resides from a <meta> tag in the HTML.

       To declare the code location, an import path of the form

	   repository.vcs/path

       specifies  the  given  repository,  with  or without the .vcs suffix, using the named version control system, and then the path inside that
       repository.  The supported version control systems are:

       Bazaar
	       .bzr

       Git
	       .git

       Mercurial
	       .hg

       Subversion
	       .svn

       For example,

	   import "example.org/user/foo.hg"

       denotes the root directory of the Mercurial repository at example.org/user/foo or foo.hg, and

	   import "example.org/repo.git/foo/bar"

       denotes the foo/bar directory of the Git repository at example.com/repo or repo.git.

       When a version control system supports multiple protocols, each is tried in turn when downloading.   For  example,  a  Git  download  tries
       git://, then https://, then http://.

       If  the	import	path is not a known code hosting site and also lacks a version control qualifier, the go tool attempts to fetch the import
       over https/http and looks for a <meta> tag in the document's HTML <head>.

       The meta tag has the form:

	   <meta name="go-import" content="import-prefix vcs repo-root">

       The import-prefix is the import path corresponding to the repository root. It must be a prefix or an  exact  match  of  the  package  being
       fetched with "go get". If it's not an exact match, another http request is made at the prefix to verify the <meta> tags match.

       The vcs is one of "git", "hg", "svn", etc,

       The repo-root is the root of the version control system containing a scheme and not containing a .vcs qualifier.

       For example,

	   import "example.org/pkg/foo"

       will result in the following request(s):

	   https://example.org/pkg/foo?go-get=1 (preferred)
	   http://example.org/pkg/foo?go-get=1	(fallback)

       If that page contains the meta tag

	   <meta name="go-import" content="example.org git https://code.org/r/p/exproj">

       the  go	tool will verify that https://example.org/?go-get=1 contains the same meta tag and then git clone https://code.org/r/p/exproj into
       GOPATH/src/example.org.

       New downloaded packages are written to the first directory listed in the GOPATH environment variable (see go-path(1)).

       The go command attempts to download the version of the package appropriate for the Go release being used.  See go-install(1) for more.

AUTHOR

       This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).

								    2012-05-13							      GO-REMOTE(7)
All times are GMT -4. The time now is 06:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy