editor for Neutrino/Photon 2.0

Robert Rutherford <ruzz@nospamplease.ruzz.com> wrote:
RR > On Thu, 5 Feb 2004 17:29:55 -0500, Adam Mallory wrote:

Set it in your .vimrc file in your home dir. Other commands of interest
might be ‘syntax on’ and ‘tags=’

RR > Also look at the :mkv command (and its variants). It lets you take your
RR > current settings and create a .vimrc from that.

RR > Also (as an aside) if you want the vim :make command to work, you need the
RR > following settings:

RR > set errorformat=%f:%l:%c:%t:%m
RR > set shellpipe=2>&1|ccfilter\ -e|tee

RR > This also requires you to have the ‘ccfilter’ program in your PATH, I can
RR > send this to you if you don’t have it.

I don’t seem to have ccfilter. Could you send it to teh address on
this post?


RR > Between this and ctags, vim is pretty much a complete IDE as far as I’m
RR > concerned :slight_smile:

RR > Did you try gvim?

RR > Rob Rutherford

Yes, I have been using gvim.

I don’t use gvim so I can’t help you out there - straight vi or vim for me,
sorry :frowning:


Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:c00f7i$ftn$1@inn.qnx.com

Adam Mallory <> amallory@qnx.com> > wrote:
AM > Set it in your .vimrc file in your home dir. Other commands of
interest
AM > might be ‘syntax on’ and ‘tags=’

AM > –
AM > Cheers,
AM > Adam

Thank you. Works great.

Let me ask one more. How can I start gvim in full screen mode?
The usual -Sm doesn’t do the trick.

On Wed, 04 Feb 2004 15:02:28 -0500, Augie wrote:

Hi.

What are some of the editor choices for programmers using Neutrino?
Something that can be started from a terminal window or Photon.

Syntax highlighting possible?

SciTE from http://www.sf.net/projects/openqnx is an option …

Armin

In article <bvv102$9rl$1@inn.qnx.com>, Julian Kinraid wrote:

Robert Rutherford <> ruzz@nospamplease.ruzz.com> > wrote:

Also (as an aside) if you want the vim :make command to work, you need the
following settings:

set errorformat=%f:%l:%c:%t:%m
set shellpipe=2>&1|ccfilter\ -e|tee

This also requires you to have the ‘ccfilter’ program in your PATH, I can
send this to you if you don’t have it.

What is ccfilter? I can’t find it on my system.

…Stephen

On 9 Feb 2004 19:53:31 GMT, Stephen Rasku wrote:

In article <bvv102$9rl$> 1@inn.qnx.com> >, Julian Kinraid wrote:
Robert Rutherford <> ruzz@nospamplease.ruzz.com> > wrote:



What is ccfilter? I can’t find it on my system.

…Stephen

On my system the source is in /usr/share/vim/vim61/tools/

You need to compile it yourself. If you get stuck I suppose I can send it
to you or post it somewhere.

Rob Rutherford

In article <mkqzst534kfy$.3pmfg02zb2pm.dlg@40tude.net>, Robert Rutherford wrote:

On 9 Feb 2004 19:53:31 GMT, Stephen Rasku wrote:

What is ccfilter? I can’t find it on my system.

…Stephen

On my system the source is in /usr/share/vim/vim61/tools/

You need to compile it yourself. If you get stuck I suppose I can send it
to you or post it somewhere.

OK, I compiled it no problem. I’ve been wanting to use the quickfix
feature of vim for awhile now. This was the missing piece. Thanks a lot.

…Stephen

AM > “Bill Caroselli” <qtps@earthlink.net> wrote in message
AM > news:c00f7i$ftn$1@inn.qnx.com

Let me ask one more. How can I start gvim in full screen mode?
The usual -Sm doesn’t do the trick.

Does anyone else know how to start gvim in full screen mode?

Bill Caroselli <qtps@earthlink.net> wrote:

AM > “Bill Caroselli” <> qtps@earthlink.net> > wrote in message
AM > news:c00f7i$ftn$> 1@inn.qnx.com> …

Let me ask one more. How can I start gvim in full screen mode?
The usual -Sm doesn’t do the trick.


Does anyone else know how to start gvim in full screen mode?

By default gvim will start as the same size as the terminal you launch
it from. You can set number of rows/columns in your .vimrc (.gvimrc).

chris


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

where is the .vimrc file located?

do you have a sample file?

what is the purpose of the ‘tags’ command? where do we get the ctag files?

TIA

Augie

“Adam Mallory” <amallory@qnx.com> wrote in message
news:bvue6b$ol4$1@inn.qnx.com

Set it in your .vimrc file in your home dir. Other commands of interest
might be ‘syntax on’ and ‘tags=’


Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net

“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:bvude1$o57$> 1@inn.qnx.com> …
Igor Levko <> spama@huxpeha.het> > wrote:
IL > Definitly vim is number one.
IL > I compiled vim6.2 for QNX4.5 with few mods - works like a charm.

Are there any decent tutorials out there?

IL > > http://www.newriders.com/books/opl/ebooks/0735710015.html
IL > > http://www.vim.org
IL > And of couse, when in vim simply try :help


I’ve been playing with vim for most of today. It isn’t too painful to
learn.

One of te first commands I had to learn was :set ts=4 to set my
displayed tab width to 4 characters instead of the default 8.

How can I save this as my default preference?

CM > By default gvim will start as the same size as the terminal you launch
CM > it from. You can set number of rows/columns in your .vimrc (.gvimrc).

CM > chris

Since I would only use gvim is runing from a photon console I’m not
launching it from a “terminal” window.

I found the commands:
set lines=
set columns=
that I can put in the .vimrc file.

This works for me.

Augie <augiehenriques@hotmail.com> wrote:
A > where is the .vimrc file located?

A > do you have a sample file?

A > what is the purpose of the ‘tags’ command? where do we get the ctag files?

A > TIA

…vimrc is located in your home directory.

Mine is included below. Most of it is the default that vim writes
out. Add anything new to the end.


ctags are used to find references to variables by name in other source
modules. I haven’t used it yet. It’s on my list of things to try.



------ .vimrc ----------

" An example for a vimrc file.
"
" Maintainer: Bram Moolenaar <Bram@vim.org>
" Last change: 2001 Jul 18
"
" To use it, copy it to
" for Unix and OS/2: ~/.vimrc
" for Amiga: s:.vimrc
" for MS-DOS and Win32: $VIM_vimrc
" for OpenVMS: sys$login:.vimrc

" When started as “evim”, evim.vim will already have done these settings.
if v:progname =~? “evim”
finish
endif

" Use Vim settings, rather then Vi settings (much better!).
" This must be first, because it changes other options as a side effect.
set nocompatible

" allow backspacing over everything in insert mode
set backspace=indent,eol,start

set autoindent " always set autoindenting on
if has(“vms”)
set nobackup " do not keep a backup file, use versions instead
else
set backup " keep a backup file
endif
set history=50 " keep 50 lines of command line history
set ruler " show the cursor position all the time
set showcmd " display incomplete commands
set incsearch " do incremental searching

" For Win32 GUI: remove ‘t’ flag from ‘guioptions’: no tearoff menu entries
" let &guioptions = substitute(&guioptions, “t”, “”, “g”)

" Don’t use Ex mode, use Q for formatting
map Q gq

" Make p in Visual mode replace the selected text with the “” register.
vnoremap p :let current_reg = @"gvs=current_reg

" This is an alternative that also works in block mode, but the deleted
" text is lost and it only works for putting the current register.
"vnoremap p "_dp

" Switch syntax highlighting on, when the terminal has colors
" Also switch on highlighting the last used search pattern.
if &t_Co > 2 || has(“gui_running”)
syntax on
set hlsearch
endif

" Only do this part when compiled with support for autocommands.
if has(“autocmd”)

" Enable file type detection.
" Use the default filetype settings, so that mail gets ‘tw’ set to 72,
" ‘cindent’ is on in C files, etc.
" Also load indent files, to automatically do language-dependent indenting.
filetype plugin indent on

" For all text files set ‘textwidth’ to 78 characters.
autocmd FileType text setlocal textwidth=78

" When editing a file, always jump to the last known cursor position.
" Don’t do it when the position is invalid or when inside an event handler
" (happens when dropping a file on gvim).
autocmd BufReadPost *
\ if line("’"") > 0 && line("’"") <= line("$") |
\ exe “normal g`”" |
\ endif

endif " has(“autocmd”)


" These additional changes were made by Bill Caroselli on Feb 06, 2004
" They should come last
set ts=4
set sw=4
set lines=90
set columns=132

I’ve been using gvim for a few weeks. It is teh best editor I’ve found
for QNX6 so far. Though it still has some quirks that I need to get
used to, I can definitely work with it.

My biggest gripe is where it puts the cursor after indenting for a new
line. For instance, I like statement blocks indented with curly braces
on a line by themselves. I.E.
if( expression )
{
// statement block
}
but after I type:
if( expression )
it puts the cursor under the ‘i’ in if. So I’ll hit once. Then
type the ‘{’. But then it inserts another for me.

What do I have to read to get a better handle on configuring auto-
indenting?

Bill Caroselli wrote:

I’ve been using gvim for a few weeks. It is teh best editor I’ve found
for QNX6 so far. Though it still has some quirks that I need to get
used to, I can definitely work with it.

My biggest gripe is where it puts the cursor after indenting for a new
line. For instance, I like statement blocks indented with curly braces
on a line by themselves. I.E.
if( expression )
{
// statement block
}
but after I type:
if( expression )
it puts the cursor under the ‘i’ in if. So I’ll hit once. Then
type the ‘{’. But then it inserts another for me.

What do I have to read to get a better handle on configuring auto-
indenting?

:help C-indenting

K.

K Neden <xxxx@yyyy.com> wrote:
KN > Bill Caroselli wrote:

What do I have to read to get a better handle on configuring auto-
indenting?

KN > :help C-indenting

I’ve re-read the whole section on C indenting several times. I’ve been
concentrating on cinoptions. It doesn’t look that difficult to
understand but everytime I try something with cino= I break something
else. I think the documentation on cinoptions sucks. It doesn’t tell
you that when you change one option it also changes other options.
There should be a sorted list of what options to change and in what
order to get the desired results.

So, it there any better documentation on cinoptions?

In article <c1og50$1r9$1@inn.qnx.com>, Bill Caroselli wrote:

K Neden <> xxxx@yyyy.com> > wrote:
KN > Bill Caroselli wrote:
What do I have to read to get a better handle on configuring auto-
indenting?

KN > :help C-indenting

I’ve re-read the whole section on C indenting several times. I’ve been
concentrating on cinoptions. It doesn’t look that difficult to
understand but everytime I try something with cino= I break something
else. I think the documentation on cinoptions sucks. It doesn’t tell
you that when you change one option it also changes other options.
There should be a sorted list of what options to change and in what
order to get the desired results.

So, it there any better documentation on cinoptions?

I am not sure exactly what you are trying to do. I use ‘smartindent’
instead of ‘cindent’. As far as I know, I am just using the default
indentexpr. Reading back in the thread, it looks like you were having
problems with brace placement. I have the following macro defined. It
might help you:

:imap { {}O

If you are still having problems getting it to work how you would like,
post a message to vim@vim.org to have the vim community help you. They
are quite helpful. Instructions on how to subscribe are at:

http://www.vim.org/maillist.php#vim

…Stephen

Stephen Rasku <spr@shaw.ca> wrote:
SR > In article <c1og50$1r9$1@inn.qnx.com>, Bill Caroselli wrote:

K Neden <> xxxx@yyyy.com> > wrote:
KN > Bill Caroselli wrote:
What do I have to read to get a better handle on configuring auto-
indenting?

KN > :help C-indenting

I’ve re-read the whole section on C indenting several times. I’ve been
concentrating on cinoptions. It doesn’t look that difficult to
understand but everytime I try something with cino= I break something
else. I think the documentation on cinoptions sucks. It doesn’t tell
you that when you change one option it also changes other options.
There should be a sorted list of what options to change and in what
order to get the desired results.

So, it there any better documentation on cinoptions?

SR > I am not sure exactly what you are trying to do. I use ‘smartindent’
SR > instead of ‘cindent’. As far as I know, I am just using the default
SR > indentexpr. Reading back in the thread, it looks like you were having
SR > problems with brace placement. I have the following macro defined. It
SR > might help you:

SR > :imap { {}O

SR > If you are still having problems getting it to work how you would like,
SR > post a message to vim@vim.org to have the vim community help you. They
SR > are quite helpful. Instructions on how to subscribe are at:

SR > http://www.vim.org/maillist.php#vim

Thank you.

I will try both of your suggestions.