OpenBSD Journal

[AskOBSDJ] development environments for OpenBSD a b x y z

Contributed by Dengue on from the mg dept.

panda writes :
"I usually use emacs as my main developping tool but i must admit that it doesn't seem like the perfect tool for OpenBSD development: there are a few KNF issues that are pretty hard to resolve with emacs even in bsd mode (c-set-style bsd). I wonder what editor/environment people developing for or with OpenBSD use. This is not meant to be yet another vi vs. emacs war, I'm just being curious."
I'm a vi guy, or alternately Xemacs with viper. But I do believe that mg(1) is a dark horse favorite in some quarters, and you can always enjoy theo.c

(Comments are closed)

Comments

  1. By Anonymous Coward () on

    ed works quite well :)

    Comments

    1. By Anonymous Cowherd () on

      Ed? Who needs all that complexity? I find that echo works quite well, and since it's usually a shell builtin you save memory too. Only people who make mistakes need full-blown editors.

      Comments

      1. By Anonymous Coward () on

        ROFL!

        Comments

        1. By Anonymous Coward () on

          I'm editing the Inodes by hand. With Magnets!!


          http://ars.userfriendly.org/cartoons/?id=19990508

  2. By danimal () on

    I don't recall where I got this (mizc@ i think) and I can't be held responsible if it's not KNF, but it works okay for me.

    -dan

    --------------------------------------------------------------

    ;; OpenBSD kernel mode
    (defun set-knf ()
    (interactive)
    (c-set-style "BSD")
    (setq c-basic-offset 8)
    (c-set-offset 'arglist-cont '*)
    (c-set-offset 'arglist-cont-nonempty '*)
    (c-set-offset 'statement-cont '*)
    (setq indent-tabs-mode 't)
    (message "OpenBSD KNF")
    )

    (global-set-key (kbd "") 'set-knf)

    Comments

    1. By Sean Cody () null@tfh.ca on mailto:null@tfh.ca

      Anyone have anything similar for vi/m?

    2. By Anonymous Coward () on

      Any feedback from the original poster on whether
      this custom emacs mode helped?

  3. Comments

    1. By ciph3r () on

      man style(9)

    2. By Anonymous Coward () on

      kernel normal form

  4. By Mikey () spikegran*earthlink!net on mailto:spikegran*earthlink!net

    I know that OBSD tends to attract the oldskool and the hardcore. Nothing wrong with that. I've written the majority of my umpteen thousand lines of code in emacs, with some vi, MS Edit, Joe, and DEC VAX edit for good measure.

    I know that emacs and vi can do anything. If I even imply differently, I'll be flamed out of existence.

    But they are ... clunky.

    Seriously, hasn't the time come to absorb some of the cool features of the IDEs into our daily methodology?

    Comments

    1. By Anonymous Coward () on

      I agree.

      I have yet to find text editor for Unix that would be as feature rich and convinient as UltraEdit for Windows. Some of the available editors are close, but still - not the same, so I stick with vi on Unix for the time being - at least it's available everywhere. :)

      Comments

      1. By Niall O'Higgins () on www.sig11.com

        I used to use UltraEdit for Windows stuff alot, I was a big fan, but I honestly find GViM much better, and now I use it under windows too!

        GViM is a seriously good editor, adds alot of the nice-ities you might miss from ViM-in-a-term.

      2. By Anonymous Coward () on

        If you insist. Whether you realize it or not you are
        within an inch of ratcheting up a flame war that hasn't
        been seen in years.
        First of all, many people here feel that emacs and
        vi ARE feature rich and convenient to use.
        And these people are correct.
        Hard to believe??
        From my own personal experience I can say this
        argument is pretty much as useful as discussing
        the benefits of eating vanilla ice cream instead of
        chocolate.
        There are 2 very different groups of people in this
        argument and they will never agree with each other.
        So Step away from the keyboard.
        get a beer. and realize in your heart of hearts
        Emacs rules. available Only at the best labs.

    2. By Anonymous Coward () on

      is good enough for editing thousand lines of code.

      >I know that emacs and vi can do anything.
      What do you mean by that? Do you mean you can use Emacs as a mailer and some insane macros you can think of?

      I just stick with pure editor with some convenience.

      Emacs is just too much for me.. To me, Emacs is like "another operating system" which has a lot of features as time goes by...

      Whereas vi editor is faster and more productive when it comes to write and edit hundred and thousand lines of code.

  5. By Generic () on

    nuff said

    Comments

    1. By Anonymous Coward () on

      you sick fuck!

  6. By Not Really Anonymous () on

    Just a thought, have you taken a look at KDevelop?

    As far as I know, I don't think there is a port for OBSD, but Im sure it will be there soon.

    I tried to compile it from the source but I ran into some issues.

    Later,
    ...

    Comments

    1. By panda () panda@NOSPAMepita.fr on mailto:panda@NOSPAMepita.fr

      I tried Kdevelop and found it to be very nice,
      the editor kinda sucks though, which is the major
      drawback of modern IDE's imho. The interface and
      functionnality is nice, but the editing capabilities
      suck. Anyway, i'm looking for gideon, the next
      generation of kdevelop, which will add support for 3rd
      party editors (like kvim).

      -- panda

  7. By Sacha () on

    I know theo.c is a part of mg(1). But how do I use the functions of it? or is just all for fun?

    Comments

  8. By Jake () on

    have you tried the plan9 IDE wily?

    /usr/ports/plan9/wily

  9. By GPS () GeorgePS@XMission.com on http://www.xmission.com/~georgeps/malephiso/screen

    I wrote my own editors out of frustration with Emacs and Vi. Malephiso is a nifty tool I whipped up that currently serves as my editor. It uses a file server and allows multiple clients to work together on the same tree. It has an embedded xterm, prototype lookup of thousands of functions, syntax highlighting, interactive chatting, an encrypted password database (via OpenSSL's crypto library) and a few other things I won't mention (see the URI/screenshot). One thing I hate about some editors is that they try to reinvent the command line, which is why I use a modified (by me) version of xterm that I embed within Malephiso. Unfortunately I'm relatively far away from 1.0, despite the fact that I use it everyday on my own projects and on itself. I still have many things I want to add such as hex editing (I've already written the widget), a hex and binary calculator, and a few other little odds and ends. I'm assuming a lot of you have written your own editors. What itch were you trying to scratch?

    Anyway, that's my 2 cents.

    George

  10. By Anonymous Coward () on

    a pretty good list to look around at is available from freshmeat:

    href="http://freshmeat.net/browse/65/?topic_id=65 .

    the things i have been looking for in an IDE are: support for the many languages i find myself coding in (C, Tcl/Tk/Itcl mainly), debugger support, and integration with CVS would be nice, too. i think i'll try and bang away at source navigator soon, which looks like it fits the bill for me.

    one i didn't see listed at freshmeat was http://oss.sgi.com/projects/jessie/ , the jessie editor from SGI's open source group. however it requires Java (1.1.7), which is available in /usr/ports/devel/jdk/1.1 ...

    some thoughts. normally i have been using a buncha xterms, vi, make/cc/tcl/etc, cvs, and gdb ... but that's growing unmanageable sometimes.

    Comments

Latest Articles

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]