Re: [ jEdit-devel ] Line numbers in the gutter

[Shlomy R. <sre...@gm...>]

On Thu, Apr 23, 2009 at 4:51 AM, Kevin Hunter <hu...@ea...> wrote:
> At 3:48pm -0400 on Wed, 22 Apr 2009, Shlomy Reinstein wrote:
>> On Wed, Apr 22, 2009 at 5:54 PM, Kazutoshi Satoda
>>> And one more thing. Please add a note about this new feature in
>>> CHANGES.txt. Doing it in the same revision with the actual change is
>>> the best practice.
>>
>> Also in r14978. The problem is, I often forget to do that.
>
> Do we need a checklist?  I note that Kazutoshi has been a good stickler
> for this and other important details.
>
> I know that checking a check-list before very commit is not exactly how
> folks like to commit (I sure don't), but it *is* a good practice from
> the maintenance and historical perspective.  Thoughts?
>

Do you mean a manual checklist, or something that's automatically
checked by SVN during commit? There is a problem with the later, since
not all commits require a change in the CHANGES.txt file. Maybe a
pop-up message as a reminder would do, but I doubt that's possible in
SVN, unless set up manually on the client side.

>> One thing no less important than this, is the update of the user docs
>> of jEdit. I don't do that both because I forget, and because I don't
>> have the infrastructure for building the jEdit docs. If this could
>> somehow be simplified, it would be great help. In this specific case,
>> I think the addition of a GUI option should be added to the user docs.
>
> I'm curious about the infrastructure bit.  I know that for Debian based
> distribution, it's a matter of 'apt-get' plus a few packages.  Would
> enumerating those packages for different distros be of help or use to
> anyone?
>

I don't think so. I had a very hard time finding out what I need,
where to get it from, and how to configure it on Windows. I think a
zip file with what's needed, with some batch file to set things up
correctly (or even an installer...) is the only reasonable way.

> Cheers,
>
> Kevin
>