> Re a text editor, what's wrong with VIM as a starting place?  I use it  
> with python consciousness (coloured keyword metatags) and it seems to  
> be easily scriptable. Admittedly, having used ED for many years, I  
> thought VI was an amazing advance. With VIM, I'm dazzled - so I might  
> be a bit out of date. :-)

Main thing is that vim is not emacs, which had colourised csound
programs way before any other.  Not sure about vim, but vi always
struck me a combining the worst features of a line editor with the
worst feature of a screen editor.

==John ffitch

"This research is of insufficient standard"

Hi!
  Sorry John to contradict here. Maybe emacs was first with colourised csound. 
But there are scripts for vim nowadays, that also enable syntax-highlighting 
for csound. And as a blind person I have to say that vim is much more 
(over-seeable) than emacs. Especially if you're used to ed. Then vim is much 
more comfortable, I believe.
  But weel here we go again into the religious debate of vim and emacs.
  So perhaps both reasonable editors and the rest is up to one's liking. Emacs 
may still have a few luxury-features, tht vim doesn't, but vim is more up to 
the basics of it.
  Kindest regards
          Julien

--------
Music was my first love and it will be my last (John Miles)

======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de

Since we're on the subject of editors, I'd like to pose a question to the
list:  What is your preferred text editor for writing Csound code?

Text editors for us Csounders is the pseudo-equivalent of our choice of
staff paper and writing utensils.  I'm personally a bit curious as to
whether some of you use a pencil or quill.  I myself use jEdit, combined
with running Csound from the terminal.  In the past, I've used bbedit,
crimson editor, and even dabbled a little in emacs.

Best,
Jake
---- 
The Csound Blog 
http://www.thumbuki.com/csound/blog/



Victor.Lazzarini wrote:
> 
> In this religious battle, I am an emacs-faithful. I could never stand ed,
> so vi and vim have never attracted me.I like the idea that you can do
> almost anything out ofemacs (except making toast perhaps).Victor-----

-- 
View this message in context: http://www.nabble.com/Editors-tp14662222p14668154.html
Sent from the Csound - General mailing list archive at Nabble.com.

I like Crimson editor a lot and at one stage I even wrote my own Csound
syntax highlighter for it. I still use it a for all my coding on windows
but for Csound I now use Lettuce.

Rory.


>
> Since we're on the subject of editors, I'd like to pose a question to the
> list:  What is your preferred text editor for writing Csound code?
>
> Text editors for us Csounders is the pseudo-equivalent of our choice of
> staff paper and writing utensils.  I'm personally a bit curious as to
> whether some of you use a pencil or quill.  I myself use jEdit, combined
> with running Csound from the terminal.  In the past, I've used bbedit,
> crimson editor, and even dabbled a little in emacs.
>
> Best,
> Jake
> ----
> The Csound Blog
> http://www.thumbuki.com/csound/blog/
>
>
>
> Victor.Lazzarini wrote:
>>
>> In this religious battle, I am an emacs-faithful. I could never stand
>> ed,
>> so vi and vim have never attracted me.I like the idea that you can do
>> almost anything out ofemacs (except making toast perhaps).Victor-----
>
> --
> View this message in context:
> http://www.nabble.com/Editors-tp14662222p14668154.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>

The problem with religious worship, is that it is based on feel-good  
and up-bringing, not logic. As a athiest (or should that be a- 
editorist) I observed previously that it's more a case of what you're  
used to. I tried emacs once and the I never got any toast out of it.  
Trouble was there was so many options that I gave up and had a piece  
of fruit instead.

Perhaps next time I have a spare couple of days I'll download the  
emacs tome and retreat to a grotto to study The Work, after which Im  
sure I'll be able to save a blank page, probably in a handful of ways.

Given emacs gloriousness, perhaps we should settle on it and then  
people can decide on the basis of what it offers to CS whether it's  
worth worshiping there. I've always thought polytheism is a much more  
sensible approach. Anyway,  I'll go to the altar of whatever  
congregation has the most interesting music.

-drw

On 08/01/2008, at 12:46 AM, Victor.Lazzarini@nuim.ie wrote:

> In this religious battle, I am an emacs-faithful. I could
> never stand ed, so vi and vim have never attracted me.
> I like the idea that you can do almost anything out of
> emacs (except making toast perhaps).
>
> Victor
>
> ----- Original Message -----
> From: Julien Claassen 
> Date: Monday, January 7, 2008 11:52 am
> Subject: [Csnd] Re: Editors
> To: csound@lists.bath.ac.uk
>
> > Hi!
> >   Sorry John to contradict here. Maybe emacs was first with
> > colourised csound.
> > But there are scripts for vim nowadays, that also enable syntax-
> > highlighting
> > for csound. And as a blind person I have to say that vim is much
> > more
> > (over-seeable) than emacs. Especially if you're used to ed. Then
> > vim is much
> > more comfortable, I believe.
> >   But weel here we go again into the religious debate of
> > vim and emacs.
> >   So perhaps both reasonable editors and the rest is up to
> > one's liking. Emacs
> > may still have a few luxury-features, tht vim doesn't, but vim
> > is more up to
> > the basics of it.
> >   Kindest regards
> >           Julien
> >
> > --------
> > Music was my first love and it will be my last (John Miles)
> >
> > ======== FIND MY WEB-PROJECT AT: ========
> > http://ltsb.sourceforge.net
> > the Linux TextBased Studio guide
> > ======= AND MY PERSONAL PAGES AT: =======
> > http://www.juliencoder.de
> >
> >
> > Send bugs reports to this list.
> > To unsubscribe, send email sympa@lists.bath.ac.uk with body
> > "unsubscribe csound"

_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 creative.canberra.edu.au/scrg/

Jacob Joaquin schreef:
> Since we're on the subject of editors, I'd like to pose a question to the
> list:  What is your preferred text editor for writing Csound code?
>   

I prefer Blue, definitely. Before that I used Notepad++ 
(), which I use for most text 
editing - no syntax coloring for CSound alas.

-- 
  Mark
  _________________________________________
  When you get lemons, you make lemonade.
  When you get hardware, you make software.

Is there a plugin for Csound in jEdit? Or how do you work for Csound  
editing in jEdit?
	joachim



Am 07.01.2008 um 16:15 schrieb Jacob Joaquin:

>
> Since we're on the subject of editors, I'd like to pose a question  
> to the
> list:  What is your preferred text editor for writing Csound code?
>
> Text editors for us Csounders is the pseudo-equivalent of our  
> choice of
> staff paper and writing utensils.  I'm personally a bit curious as to
> whether some of you use a pencil or quill.  I myself use jEdit,  
> combined
> with running Csound from the terminal.  In the past, I've used bbedit,
> crimson editor, and even dabbled a little in emacs.
>
> Best,
> Jake
> ----
> The Csound Blog
> http://www.thumbuki.com/csound/blog/
>
>
>
> Victor.Lazzarini wrote:
>>
>> In this religious battle, I am an emacs-faithful. I could never  
>> stand ed,
>> so vi and vim have never attracted me.I like the idea that you can do
>> almost anything out ofemacs (except making toast perhaps).Victor-----
>
> -- 
> View this message in context: http://www.nabble.com/Editors- 
> tp14662222p14668154.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"

As far as I am aware, there is no Csound plugin for jEdit.  Though it is
possible to create a syntax highlighting scheme for Csound, I've never
gotten around to it.  If there is interest in this, let me know, and I'll
see what I can do.

My general work flow is this.  I'm an OS X user.  I use jEdit as my primary
text editor.  And I use the command-line to run all my Csound jobs.

The thing I like about jEdit, is that it allows me to do most of my Csound
coding while rarely having to touch a mouse, as the mouse can be a huge
source of pain for my right wrist after prolonged use.  This pain is the
reason why I haven't thoroughly explored software like Blue and MaxMSP.  I'm
also not going to accidently hit some magical key-combination and enter into
some eccentric editing mode that I don't know how to get out of, as is often
the case with emacs.  :)

Though I tend to work with csd files rather than the traditional orc and sco
pair, when these files start to grow, I tend to split them into multiple
files.  For example, after splitting foo.csd, I would have foo.csd,
foo.score, foo.macro, foo.opcode.  I then use the #include opcode in the
appropriate places.  jEdit, like any good text editor, allows me to rotate
through all these open files with keyboard short-cuts.

I use the terminal for a number of reasons.  In my experience, it runs
noticeably faster than Csound5GUI.  I can also use a keyboard short-cut to
switch between jEdit and the terminal, eliminating have to use the mouse. 
Once I'm in the terminal, pressing the up arrow recalls the last command
entered, so I don't have to type "csound -d -odac foo.csd" everytime I run a
job.  I can also have multiple terminal windows running, each with a
different csound job on deck, or for running home-brewed perl scripts.

Back in the day, when I was still on windows, I would use a similar
configuration with Crimson Editor and cygwin.  The reason why I started
using jEdit is because it is very similar to Crimson editor, with the bonus
that it was cross-platform.


"Too much information, man!"


Anyways, I hope I haven't bored anyone.  :)

Best,
Jake 
---- 
The Csound Blog 
http://www.thumbuki.com/csound/blog/



joachim heintz wrote:
> 
> Is there a plugin for Csound in jEdit? Or how do you work for Csound  
> editing in jEdit?
> 	joachim
> 

-- 
View this message in context: http://www.nabble.com/Editors-tp14662222p14691202.html
Sent from the Csound - General mailing list archive at Nabble.com.

Thanks, Jake. I personally work with MacCsound, and I am satisfied  
with the text editor there. But for the reasons
1) if the problems with a UB version could not be solved, and
2) for the sake of being cross-platform (especially because I am  
teaching) -
I am slightly looking for an other possibility. So if you think it's  
possible to make syntax highlighting and a good connection between  
jEdit and the Csound Manual, I would be interested in this.
Best -
	joachim



Am 08.01.2008 um 15:55 schrieb Jacob Joaquin:

>
> As far as I am aware, there is no Csound plugin for jEdit.  Though  
> it is
> possible to create a syntax highlighting scheme for Csound, I've never
> gotten around to it.  If there is interest in this, let me know,  
> and I'll
> see what I can do.
>
> My general work flow is this.  I'm an OS X user.  I use jEdit as my  
> primary
> text editor.  And I use the command-line to run all my Csound jobs.
>
> The thing I like about jEdit, is that it allows me to do most of my  
> Csound
> coding while rarely having to touch a mouse, as the mouse can be a  
> huge
> source of pain for my right wrist after prolonged use.  This pain  
> is the
> reason why I haven't thoroughly explored software like Blue and  
> MaxMSP.  I'm
> also not going to accidently hit some magical key-combination and  
> enter into
> some eccentric editing mode that I don't know how to get out of, as  
> is often
> the case with emacs.  :)
>
> Though I tend to work with csd files rather than the traditional  
> orc and sco
> pair, when these files start to grow, I tend to split them into  
> multiple
> files.  For example, after splitting foo.csd, I would have foo.csd,
> foo.score, foo.macro, foo.opcode.  I then use the #include opcode  
> in the
> appropriate places.  jEdit, like any good text editor, allows me to  
> rotate
> through all these open files with keyboard short-cuts.
>
> I use the terminal for a number of reasons.  In my experience, it runs
> noticeably faster than Csound5GUI.  I can also use a keyboard short- 
> cut to
> switch between jEdit and the terminal, eliminating have to use the  
> mouse.
> Once I'm in the terminal, pressing the up arrow recalls the last  
> command
> entered, so I don't have to type "csound -d -odac foo.csd"  
> everytime I run a
> job.  I can also have multiple terminal windows running, each with a
> different csound job on deck, or for running home-brewed perl scripts.
>
> Back in the day, when I was still on windows, I would use a similar
> configuration with Crimson Editor and cygwin.  The reason why I  
> started
> using jEdit is because it is very similar to Crimson editor, with  
> the bonus
> that it was cross-platform.
>
>
> "Too much information, man!"
>
>
> Anyways, I hope I haven't bored anyone.  :)
>
> Best,
> Jake
> ----
> The Csound Blog
> http://www.thumbuki.com/csound/blog/
>
>
>
> joachim heintz wrote:
>>
>> Is there a plugin for Csound in jEdit? Or how do you work for Csound
>> editing in jEdit?
>> 	joachim
>>
>
> -- 
> View this message in context: http://www.nabble.com/Editors- 
> tp14662222p14691202.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"

Yes and maybe.

When I couldn't sleep last night, I spent time with syntax highlighting
feature of jEdit and came up with a descent mode for Csound.  Without doing
to much work, it seems to already work fairly well.  I think getting it just
right will take some time.  I'll play with it on and off through out the
day, and if I get it in a place I like, I'll put it up here.

As for a good connection between jEdit and the Csound manual, it really
depends on a few factors.  I'm assuming that the key feature, and let me
know if I'm wrong, would be the ability to open the manual based on the
current highlighted opcode.  I do believe this is possible with a jEdit
plugin.  However, it looks like it would take up to much of my personal time
to implement.  There may an easier solution using macros || the bean shell,
which I'll look into today.

Best, 
Jake 
---- 
The Csound Blog 
http://www.thumbuki.com/csound/blog/




joachim heintz wrote:
> 
> ...I am slightly looking for an other possibility. So if you think it's  
> possible to make syntax highlighting and a good connection between  
> jEdit and the Csound Manual, I would be interested in this.
> Best -
> 	joachim
> 

-- 
View this message in context: http://www.nabble.com/Editors-tp14662222p14713347.html
Sent from the Csound - General mailing list archive at Nabble.com.

Jacob Joaquin wrote:

> Since we're on the subject of editors, I'd like to pose a question to the
> list:  What is your preferred text editor for writing Csound code?

Blue! And emacs before that.

But that's not only text editor. The most important thing for me is that 
it makes it easy to encapsulate instruments + the build in python 
intrepreter. I also think the graphical interface to instruments makes 
it possible to make just the right abstraction so that instruments are 
both versatile, easy to tweak and easy to "just use".

-- 
peace, love & harmony
Atte

http://atte.dk       | http://myspace.com/attejensen
http://anagrammer.dk | http://modlys.dk

I just finished the very first syntax highlighting mode for jEdit.  As of
right now, it only supports CSD files.  Once this has been thoroughly
tested, I will add ORC and SCO support.  Which won't take much time to do.


Csound Mode for jEdit 4.2  Version 0.1
http://www.thumbuki.com/csound/files/mailinglist/jEditCsoundModev0.1.zip


If you find any bugs, or see anything that isn't highlighted that should be,
let me know.  And I just realized that I'm a little behind in the Csound
version department, so any opcodes that are exclusive to 5.06 or greater
will not be highlighted.  I'll be sure to fix that in the first upgrade.

Best, 
Jake 
---- 
The Csound Blog 
http://www.thumbuki.com/csound/blog/



Jacob Joaquin wrote:
> 
> When I couldn't sleep last night, I spent time with syntax highlighting
> feature of jEdit and came up with a descent mode for Csound.  Without
> doing to much work, it seems to already work fairly well.  I think getting
> it just right will take some time.  I'll play with it on and off through
> out the day, and if I get it in a place I like, I'll put it up here.
> 

-- 
View this message in context: http://www.nabble.com/Editors-tp14662222p14723061.html
Sent from the Csound - General mailing list archive at Nabble.com.

Jake -

this works fine. Thanks for giving this. So I'm not sure if I shall  
wish better sleep at night or not ...
Best -

	joachim



Am 09.01.2008 um 23:19 schrieb Jacob Joaquin:

>
> I just finished the very first syntax highlighting mode for jEdit.   
> As of
> right now, it only supports CSD files.  Once this has been thoroughly
> tested, I will add ORC and SCO support.  Which won't take much time  
> to do.
>
>
> Csound Mode for jEdit 4.2  Version 0.1
> http://www.thumbuki.com/csound/files/mailinglist/ 
> jEditCsoundModev0.1.zip
>
>
> If you find any bugs, or see anything that isn't highlighted that  
> should be,
> let me know.  And I just realized that I'm a little behind in the  
> Csound
> version department, so any opcodes that are exclusive to 5.06 or  
> greater
> will not be highlighted.  I'll be sure to fix that in the first  
> upgrade.
>
> Best,
> Jake
> ----
> The Csound Blog
> http://www.thumbuki.com/csound/blog/
>
>
>
> Jacob Joaquin wrote:
>>
>> When I couldn't sleep last night, I spent time with syntax  
>> highlighting
>> feature of jEdit and came up with a descent mode for Csound.  Without
>> doing to much work, it seems to already work fairly well.  I think  
>> getting
>> it just right will take some time.  I'll play with it on and off  
>> through
>> out the day, and if I get it in a place I like, I'll put it up here.
>>
>
> -- 
> View this message in context: http://www.nabble.com/Editors- 
> tp14662222p14723061.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"