RE: Evergreen and gvim

[Martin Dorey]

+list

 

If you think it's sane, dude, it's sane.  (I'm sure someone will ask why you want gvim but I'll ignore that as I think there are two constructive things to get from this before we get to that.)

 

Would anyone be motivated to do it?  If you supplied a patch, though, even a botched one (http://wiki.dev.bluearc.com/wiki/index.php/Jargon_buster#Morton)...

 

I see that we do pop an error window even when there are no errors to put in it.  This is mildly annoying elsewhere too - I'm thinking of my Shell Window action.  I haven't looked but I'd be surprised if there were any reason for that except that it's the simplest thing that could work.  Addressing that sounds like it might fix your case too, by just doing The Right Thing without the need for configuration with ":", in true Jessies style.  Now you've made me think of it, I'm almost keen enough to look myself, but then that would scupper the opportunity to get you looking at the code.  One of the main goals was that it should be fun to hack on (which is one reason behind the philosophy of keeping the number of options low).  And you're a professional Java programmer, where I just tinker.  The Building from Source commands from under http://software.jessies.org/evergreen/#downloads will work for you out-of-the-box on hover.us.dev.bluearc.com.  I know this, because I just tried them :), found they needed libx11-dev and installed it for you.  Half hour job for a man of your caliber.  If it weren't patronizing, I'd suggest creating the window invisible and making it visible (or showable or whatever the hell it's called) whenever we put stuff in it.  It'd be, like, two lines, wouldn't it?

 

---

From: Alan Carwile
Sent: Friday, June 10, 2011 10:15
To: Martin Dorey
Subject: Evergreen and gvim

 

Martin – could you do a sanity check on this post which I’m thinking of sending to the evergreen users group list?

 

 

I setup evergreen so it can launch gvim (graphical vim) from a popup menu on a file in evergreen.  I used the ! option but it always launches a build output window too.  I’d like to avoid having a build output window every time I use this external tool. I’d like to propose that an option be added like “:” which would launch the command but not provide any stdin and not do anything with stdout.  When finish editing with gvim, I use “Revert to Saved” to update the file in evergreen.

 

If I switch to “<”, it puts stdout in place of whatever was selected in the file – obviously not so good.  The other options also don’t seem to do what I want.

 

Could something like this be added, or does someone have a workaround for this, to get rid of the “bogus” build output window when launching the external tool?

 

My gvim.tool file contains:

   name=VIM current file

   command=!gvim $EVERGREEN_CURRENT_FILENAME

   showOnPopUpMenu=true

   checkEverythingSaved=true

   needsFile=true

 

Thanks

 

I do not see a request like this in the group.

 

Alan

[Elliott Hughes]

martin's show-on-demand idea sounds like a generally good thing
(though we might decide otherwise after actually having used it!) and
does sound like it would address your complaint (in a way that means
it'll "just work" for anyone trying to do anything similar in future).

iirc, Mosaic used to behave like martin describes rather than what i
actually implemented, despite the fact that i was thinking of Mosaic
when i wrote it. he's probably right about it only being the way it is
because that was the easiest thing to implement (and because it was
fine for my motivating examples).

> --
> You received this message because you are subscribed to the Google Groups
> "evergreen-users" group.
> To post to this group, send email to evergre...@googlegroups.com.
> To unsubscribe from this group, send email to
> evergreen-use...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/evergreen-users?hl=en.
>

--
Elliott Hughes - http://www.jessies.org/~enh/

[Alan Carwile]

I appreciate the compliment/challenge but can't take it on at this time. Perhaps someone else on the list will wish to do so.
Thanks,
Alan

[Alan Carwile]

Reconsidering a bit. I did not find a project file for use with Intellij IDEA in the svn checkout. Anybody got one? I asked IDEA to generate one based on the source files but need to get the libraries/sdk's right. Else lots of classes aren't known. Anyone done that?

Thanks,
Alan

> Martin - could you do a sanity check on this post which I'm thinking of

> sending to the evergreen users group list?
>
> I setup evergreen so it can launch gvim (graphical vim) from a popup menu on
> a file in evergreen.  I used the ! option but it always launches a build
> output window too.  I'd like to avoid having a build output window every
> time I use this external tool. I'd like to propose that an option be added
> like ":" which would launch the command but not provide any stdin and not do
> anything with stdout.  When finish editing with gvim, I use "Revert to
> Saved" to update the file in evergreen.
>
> If I switch to "<", it puts stdout in place of whatever was selected in the

> file - obviously not so good.  The other options also don't seem to do what

> I want.
>
> Could something like this be added, or does someone have a workaround for
> this, to get rid of the "bogus" build output window when launching the
> external tool?
>
> My gvim.tool file contains:
>
>    name=VIM current file
>    command=!gvim $EVERGREEN_CURRENT_FILENAME
>    showOnPopUpMenu=true
>    checkEverythingSaved=true
>    needsFile=true
>
> Thanks
>
> I do not see a request like this in the group.
>
> Alan

--

[Elliott Hughes]

i don't think so. i think there's Eclipse configuration (though maybe
only for Terminator).

i'd guess your problem is that you need to tell Intellij about the
salma-hayek source tree too.

--

[Alan Carwile]

Elliott - You're right. I recreated the project in IDEA and had it include salma-hayek source as well. Building in IDEA generated a runnable evergreen program which I can step through in the debugger. However, it starts up and tells me it must be the first time I've run evergreen because it apparently doesn’t understand where the info is saved about the workspaces I defined (7-8 of them).
Welcome to Evergreen
This looks like the first time ...
This seems to be because I did not define a property when building evergreen, used by:

public static String getResourceFilename(String... components) {
return System.getProperty("org.jessies.projectRoot") + File.separator + StringUtilities.join(components, File.separator);
}

Evergreen ends up looking in a directory called "null/..." if this property is not set.

If I run it outside the debugger, it understands my workspaces and loads up the tabs, etc. This is by "cd ~/jessies/evergreen/bin; ./evergreen &

I tried "make clean; make" outside the debugger, but inside IDEA it still fails as noted, thinking it is the first time it has been run.

Suggestions?

[Martin Dorey]

Bumped into Alan in the kitchen and explained.