evergreen-users

Hi again. It's been a while. The hacky auto-complete solution I mentioned in my last email is

Hi. Yep, I remember the "try to act like others" principle - there are even comments

On Sat, Feb 13, 2021, 02:53 Phil Norman <phil...@gmail.com> wrote: On Sat, 13 Feb 2021 at 02:

That did the trick for the nightlies, ta. On Sat, Dec 19, 2020 at 06:56 Phil Norman <philnorm@

Hi again. I've merged 'nio' back into the main branch. Thanks very much to ritschwumm for

Hi again. I've continued to work on the "nio" branch. So far it contains the following

I finally got around to diffing the highlights. The deferral did indeed help a lot, but I've

I don't think I've ever successfully used Open Import. On Mon, Nov 26, 2018 at 07:23 Phil

martind@swiftboat:~$ dpkg --status clang-format-3.8 | grep Status Status: install ok installed

That's maddening. I can't understand that without the original check-in comment, https://

On Sun, Sep 16, 2018 at 7:15 AM Phil Norman <phil...@gmail.com> wrote: On 15 September 2018 at

(Ta. I am ~around but the code's at work and I had the fix already, so it didn't seem urgent.

It turns out that ninja already does the same "Entering directory" as make, so I've

On Sun, Jul 29, 2018 at 1:37 AM Phil Norman <phil...@gmail.com> wrote: On 29 July 2018 at 03:

i fixed F1 for man pages yesterday and tried to make use of it at work today and was ... underwhelmed

On Tue, Jul 3, 2018 at 11:57 AM Martin Dorey <marti...@gmail.com> wrote: > > > am i

Uncaught exception An error occurred in Evergreen: Exception RuntimeError: Java failed with #<

Hi. Just pushed a little change to the tool handling. I've added a new prefix, "|?".

On 13 February 2018 at 03:48, Martin Dorey <marti...@gmail.com> wrote: > 1: Clicking on

I've had a few dead Evergreens in the last few months. I don't think I've seen this

The indenter is my only gripe. It's not perfect on my code but a pain on some other styles. I

It worked! Thanks a lot :-) In addition to the go syntax highlighter I wrote way back when, last

I suspect this is the usual Java error, but will let you sort it. I had done a <CTRL-O> and

Simon lives! I recently got the jessies stuff up at github, writing [ I've got the history copied

> this is the indexing rather than the find in files? Yes. >> I've got a threaded Ruby

"stuttery". not smooth. i also found that if i clicked on a Find in Files match i got dark

Exited evergreen and restarted it. Then the operation worked and I did not get this traceback. Alan

> It only reads the file with the Built date when it needs to show an alert. The file might have

> would everyone be better off if we just removed that line? No, per Neil below, but I did it

2 is the google style guide value. Probably just an oversight because that was convenient for his