On Tue, Sep 9, 2014 at 8:25 AM, Tony Papadimitriou wrote:
>So, I would like to see this improvement, if possible: Once launched,
> the window to come in front of other windows, and its position to be always
> centered.
>
FWIW: if this change is made, i'd request that it only be made on Wind
Hello,
The --TK option of the DIFF command brings up a window with the side by side
comparison of the files but (on Win7 at least), this window is not in the
foreground, and it also always moves location (from invocation to invocation)
so that sometimes part of it even falls outside the screen.
On Tue, Sep 9, 2014 at 12:17 AM, Ron W wrote:
> I think perhaps your experimental subjects are expecting that to be the
> answer.
>
Very possibly.
> I think a better experiment might be to find a complex change one of them
> made, then ask them to explain to you what they were trying to do.
>
On Mon, Sep 8, 2014 at 6:56 PM, Paul Higham wrote:
> I recently upgraded to Fossil version 1.29 and I love both the ability to
> do wysiwyg editing of wiki pages and the flexibility to use Markdown as
> well.
>
> However, I would like to see this capability applied to the ticket
> description fie
I recently upgraded to Fossil version 1.29 and I love both the ability to do
wysiwyg editing of wiki pages and the flexibility to use Markdown as well.
However, I would like to see this capability applied to the ticket description
field as well - is there any hope for this? Or is it already ther
On Mon, Sep 8, 2014 at 1:18 PM, Stephan Beal wrote:
> The answer, invariably (and correctly), is "go look up that ticket number
> in Jira."
>
> RIGHT!
>
> But they still don't like seeing it. Seems to be just a force of habit.
>
I think perhaps your experimental subjects are expecting that to be
On Mon, Sep 8, 2014 at 7:14 PM, Ron W wrote:
> On Mon, Sep 8, 2014 at 12:32 PM, Stephan Beal
> wrote:
>
>> In my experience a ticket number is the longest-lasting/maintainable
>> approach (though _all_ of my colleagues complain when i do it,
>>
>
> What don't they like about putting ticket IDs i
On Mon, Sep 8, 2014 at 12:32 PM, Stephan Beal wrote:
> In my experience a ticket number is the longest-lasting/maintainable
> approach (though _all_ of my colleagues complain when i do it,
>
What don't they like about putting ticket IDs in the code comments?
_
On 9/8/2014 08:51, Richard Hipp wrote:
On Mon, Sep 8, 2014 at 10:49 AM, Warren Young mailto:war...@etr-usa.com>> wrote:
I wish it would not collapse double newlines.
Have you tried selecting the "Allow block-markup in timeline" option on
the Admin/Timeline page ?
Beautiful, thanks!
That
On Mon, Sep 8, 2014 at 6:26 PM, Ron W wrote:
> On the fix description side, I put any detail commentary in the source
> comments and include a reference to the ticket. Even if you
>
In my experience a ticket number is the longest-lasting/maintainable
approach (though _all_ of my colleagues compl
On Mon, Sep 8, 2014 at 10:49 AM, Warren Young wrote:
> Sometimes one of my commit messages actually stretches to the point of
> needing paragraphs, either because the problem it fixes is particularly
> complex or because the solution/feature is.
On the problem description side, I use tickets -
On Mon, Sep 8, 2014 at 10:49 AM, Warren Young wrote:
the timeline compresses whitespace in commit messages, so you can't see
> paragraph breaks without digging down into the individual checkin. I wish
> it would not collapse double newlines.
>
Have you tried selecting the "Allow block-markup in
On 9/7/2014 17:10, Will Parsons wrote:
I have to admit that I *hate* to mistype a commit message and have it
frozen for all time. Using an editor just seems so much easier...
Fossil lets you edit commit messages. In true Fossil fashion, the old
message isn't overwritten, just *overridden*,
Hi fossilers,
I'm trying to implement checkboxes within tickets using TH1. First question --
has anyone managed to do this?
In common I have:
set status_choices {New
Features
Uninteresting}
While the database column is "status". I've tried the following:
for {set i 0} {$i < [linecount $stat
On 06/09/14 17:03, Richard Hipp wrote:
> I'll let Scott answer the specific question. But I just want to remind
> Miles of the "Embedded Documentation" feature of Fossil
> (http://www.fossil-scm.org/fossil/doc/tip/www/embeddeddoc.wiki) and that
> the main Fossil website including all of the on-li
15 matches
Mail list logo
