On Thu, Oct 07, 2010 at 11:41:00AM -0700, docgnome wrote:
> At Thu, 7 Oct 2010 20:10:04 +0300,
> Nicholas Ochiel wrote:
> >
> > I've just started looking through the conkeror source and I was
> > wondering: What does your development pipeline look like? i.e. I
> > assume maintainers use emacs/vi but could you describe what other
> > tools you use, and how they are integrated, how you go about debugging
> > conkeror, (incrementally) testing code, etc.
>
> I can't speak for anyone else but MozRepl is handy for debugging.
> http://github.com/bard/mozrepl/wiki
>
> Dave
I second the vote for mozrepl. I use it constantly. I use emacs for an
editor, in which I have set up some key bindings..
C-c F set-project: sets the root directory for 'C-c f', and also
generates an etags file in ~/TAGS for quick jumping to
definitions with 'M-.'
C-c f find-file-in-current-project
I have one or two terminal sessions in tmux for running
conkeror.. sometimes one for web browsing and one for testing, depending
on how complex the thing I'm working on at the moment is. Then I also
tend to have one or two term-mode buffers in emacs where I operate git and
other conkeror-related file operations.
I use both gitk and git gui, in addition to the command line git tools.
--
John Foerch
_______________________________________________
Conkeror mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/conkeror
