Re: [fossil-users] BISECT LOG displays UTC date/time even though timeline is set to local date/time

[Marko Käning]

Hi Tony,

I think your finding is something like I’ve spotted also in the ticket overview 
pages [1].

This needs someone willing to submit a patch fixing these issues… Sorry, I 
hadn’t found the time to deal with this myself up to now.

Greets,
Marko



[1] http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg23088.html




On 21 Jun 2016, at 09:13 , Tony Papadimitriou  wrote:

> This is fossil version 1.35 [3aa86af6aa] 2016-06-14 11:10:39 UTC
>  
> It’d be less confusing if BISECT displayed the date/time the same way as the 
> current timeline setting.
>  
> Thanks.
>  
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Preferred way of dealing with upstream projects maintained in different VCSes?

[Marko Käning]

On 16 Jun 2016, at 04:02 , lvh <_...@lvh.io> wrote:
> I’m interested in exploring the possibilities of moving to a Fossil monorepo 
> at $dayjob. One of the things I’m not sure how to deal with appropriately is 
> dealing with projects managed upstream in some other VCS (which, de facto, 
> appears to be just git). For example, I’m currently working on Azure 
> (Microsoft’s cloud) using REST APIs, defined by a bunch of Swagger files 
> (https://github.com/Azure/azure-rest-api-specs).
> 
> These are important to the software we’re building, so they ought to live in 
> VCS, or at least a reference to them should. How do you manage this? Just put 
> the .git dir in version control? Bare checkout? Something that references the 
> repo + commit but keeping the actual checkout out of source control?

I usually simply copy the git clone into the fossil repo.
The .git dir is not checked into the fossil repo, instead I commit the whole 
folder into fossil as well.
From then on one can keep the same folder structure synced in git as well as 
fossil.
Can become messy if you’re not attentive, but works. Cross referencing the 
commit hashes in commit messages of the DVCS counterparts makes sense too. ;-)

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Suggestions for list of branches in web-UI

[Marko Käning]

On 24 May 2016, at 23:42 , Marko Käning <sec001+fos...@posteo.net> wrote:

> My initial point 1) is still open for discussion:
> 
>> 1) It would be nice, if private branches were marked in /brlist somehow, 
>> preferably
>> by introducing a new column entitled “Private”, or stg similar.
> 
>   Anyone out there having a comment for that?

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Pushing and pulling of ticket reports

[Marko Käning]

Hi,

On 30 May 2016, at 00:04 , Marko Käning <sec001+fos...@posteo.net> wrote:

> My question was where I find documented which areas are automatically 
> pushed/pulled
> and whether one can make it clearer perhaps even in the “fossile config pull 
> help”
> or/and something more appropriate.

any feedback on this?

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How to search for changes in checkins?

[Marko Käning]

Hi Richard,

On 09 Jun 2016, at 17:16 , Richard Hipp  wrote:
> I've long thought that this would be a very useful feature to add.

+1


> (1) A full-text index uses roughly 30% as much disk space as the
> content that is being indexed.  (This is a mathematical property of
> full-text search - not a deficiency in Fossil's implementation.)
> Doing full text search on all check-in diffs might result in a very
> large search index.

Well, 30% isn’t an issue in most cases, I figure.


> (4) Initializing the search index means computing all historical
> check-in diffs.  That might take a while.  Figure about 10 check-ins
> per second.  Fossil itself currently has 9506 check-ins, so total
> initialization time would be 15 minutes.  (The "10 checkins per
> second" number is a guess.  Processing might go significantly faster.
> We will need to experiment to know.)

One could make this indexing optional, perhaps, no? A bit like the
indexing of Wiki/Docu/Tickets info in the UI…

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Adding 'bz2' and 'bzip' to mimetypes

[Marko Käning]

Now that we’re at it…

On 09 Jun 2016, at 21:38 , Warren Young  wrote:

> On Jun 9, 2016, at 9:04 AM, Tomek Kott  wrote:
>> 
>> Any chance that 'bz2' and 'bzip' could be added to the 'official' fossil 
>> types? (http://fossil-scm.org/index.html/artifact/aad06cde815b7051?ln=71-288)
> 
> If so, then xz should be added, too.  It’s becoming quite popular.

… what about 7z?

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] web-UI's timeline should use non-proportional font for commit hashes

[Marko Käning]

Hi Ron,

On 25 May 2016, at 18:07 , Ron W  wrote:

> Fossil has the capability for user defined "skins". Never used it myself, but 
> I have seen some nice custom skins for Fossil.

I know. I was using them to defined the font in its CSS section.


> BTW, I assume CSS has styling modifiers, so I'd probably use "font-style" (or 
> whatever it is) to specify "monospaced”.

Yeah, it would be “monospace” without a trailing ‘d’, but “courier” actually 
looks better, as its font size is matching.

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Suggestions for list of branches in web-UI

[Marko Käning]

Hi Ron,

On 25 May 2016, at 18:00 , Ron W  wrote:
> I didn't know private branches had a default name. I thought creating any new 
> branch
> required supplying a name.

no, if you create a new private branch by using the '--private’ option then the 
branch will
be automagically be named as “private”.



> But yes, branch names can be re-used. This is because branches are identified 
> by tags
> on commits. While a special table could be used to prevent this, no one has 
> had enough
> of a problem with this to warrant impeding re-use of branch names.

Well, in this specific case I don’t have to much of a problem with is. The 
weirdness is here
only that completely unrelated private subbranches get thrown together locally.

This, of course, isn’t a big problem, as these private branches are not meant 
to be kept
anyways. But I thought I mention it.

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Pushing and pulling of ticket reports

[Marko Käning]

Hi Richard,

On 25 May 2016, at 05:38 , Richard Hipp <d...@sqlite.org> wrote:
> fossil config push ticket
> fossil config pull ticket

yes, I am aware of that, which is why I wrote this post in the first place.


>> On 14 May 2016, at 12:55 , Marko Käning <sec001+fos...@posteo.net> wrote:
>> 
>>> It seems like the ticket area - which contains the ticket reports - is not
>>> pushed/pulled automatically to the parent repository (just like skin
>>> area)...
>>> 
>>> What is the reason for that and where are these exceptions actually
>>> documented?
>>> Can’t find it anywhere at the moment, but remember to have seen it
>>> somewhere (for
>>> the skin area). Perhaps I’ve spotted this only on the mailing list even.

My question was where I find documented which areas are automatically 
pushed/pulled
and whether one can make it clearer perhaps even in the “fossile config pull 
help”
or/and something more appropriate.

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] web-UI's timeline should use non-proportional font for commit hashes

[Marko Käning]

Hi,

I just noticed that the Fossil’s web-UI’s timeline uses a proportional font
when rendering the commit messages. These are prefixed by shortened commit
hashes. Although all these have a length of 10 characters, they’ve different
rendered lengths in pixels which lets the timeline appear somewhat rough on
the left. I prefer to see all commit messages nicely left-aligned though...

Thus “a.timelineHistLink” is my friend and I’ve added this to the CSS
section of my skin:

---
a.timelineHistLink {
  font-family: courier;
}
---

That makes the timeline look better! ;-)

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Suggestions for list of branches in web-UI

[Marko Käning]

Thanks Baruch, for the clarification so far!

My initial point 1) is still open for discussion:

> 1) It would be nice, if private branches were marked in /brlist somehow, 
> preferably
> by introducing a new column entitled “Private”, or stg similar.

Anyone out there having a comment for that?


BTW, I have noticed that there can be more than one private branch 
(automatically) named “private”…

They all appear then under the link ‘private’ in the "branch name” column.

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Pushing and pulling of ticket reports

[Marko Käning]

Hi list,

anyone who knows more about this?

On 14 May 2016, at 12:55 , Marko Käning <sec001+fos...@posteo.net> wrote:

> It seems like the ticket area - which contains the ticket reports - is not 
> pushed/pulled automatically to the parent repository (just like skin area)...
> 
> What is the reason for that and where are these exceptions actually 
> documented? 
> Can’t find it anywhere at the moment, but remember to have seen it somewhere 
> (for
> the skin area). Perhaps I’ve spotted this only on the mailing list even.

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Pushing and pulling of ticket reports

[Marko Käning]

Would be nice if this
---
$ fsl config pull help
Available configuration areas:
  email  Concealed email addresses in tickets
  projectProject name and description
  skin   Web interface appearance settings
  cssStyle sheet
  shun   List of shunned artifacts
  ticket Ticket setup
  user   Users and privilege settings
  xfer   Transfer setup
  allAll of the above
no such configuration area: “help"
---
would explicitly mark all the areas which are auto-synched, no!?
:)


The configuration command help page should also mention the defaults.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to render a vertical line in a Markdown code snippet?

[Marko Käning]

How to render a vertical line in a Markdown code snippet?

I tried `|`, `\|` and `||` but all to no avail. The bare vertical in text flow 
even caused fossil’s UI to try to render a table at one point.

If I do the same in a multiline code block it works:
`
|
`
but how to get this done w/o trouble in a code snippet??
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Pushing and pulling of ticket reports

[Marko Käning]

It seems like the ticket area - which contains the ticket reports - is not 
pushed/pulled automatically to the parent repository (just like skin area)...

What is the reason for that and where are these exceptions actually documented? 
Can’t find it anywhere at the moment, but remember to have seen it somewhere 
(for
the skin area). Perhaps I’ve spotted this only on the mailing list even.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] No progress on "fossil cp"

[Marko Käning]

Hi Stephan,

On 14 May 2016, at 12:35 , Stephan Beal  wrote:
> But in svn, now that i think about it, cp is, in practice, only used for 
> branching. i've never seen it used to copy something within the same tree.

maybe. So, I might have abused it all along. :)


> That would require a backwards-incompatible change to the manifest format, 
> which would bring with it a lot of pain for a feature which seems to be only 
> rarely useful (and never critical).

Yeah, forget it. I’ll keep info in the commit message if I need it, which 
happens rarely enough.

Thanks for caring!
Greets,
Marko___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Cloning failure via SSH on MSYS2

[Marko Käning]

Hi,

on an MSYS2 install I was trying to clone a repo which I can reach via SSH like 
this
---
$ fossil clone ssh://marko@IP:PORT//home/REPOS/FOSSIL/test.fossil test.fossil
The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 2048 78:83:99:b2:AA:87:5B:a9:05:81:12:f7:97:9f:77:c0
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n) y
---

SSH is correctly configured, as I can log onto the host no problem, but above 
clone 
hangs once I press the "y" and then RETURN.

What's going on here?

It could be, that I have a firewall issue on that machine, so I don’t want to
point a finger on Fossil. Fossil but might be able to give me some info about 
the
hang. How can I see more (debug) information in order to understand which 
process
is the blocking one?


Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] No progress on "fossil cp"

[Marko Käning]

On 14 May 2016, at 12:11 , Stephan Beal  wrote:
> in 20+ years of using source control, i've never seen an 'cp' command (maybe 
> i've just overlooked it in CVS/SVN). Fossil does have an 'mv' command which 
> does retain history. Copying the same file to multiple places, while keeping 
> the history for each and every copy, seems highly questionable to me.

SVN and Mercurial have a copy command which keeps history.


> consider:
> 
> scm cp a b
> 
> now my history looks like 'b' has existed as long as 'a' has, which would be 
> a bald-faced lie.

Admittedly. :)


> Checking out an older version, from before the copy, would presumably _not_ 
> want to check out 'b', but retaining its history would imply that 'b' should 
> indeed be retroactively applied to checkouts of any version which contains 
> 'a’.

Well, I guess in Fossil one will simply have to leave a not in the commit 
message from where a specific
copied file originates then. :)

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Feature request: auto-closing of tickets a la Trac

[Marko Käning]

On 13 May 2016, at 18:58 , Warren Young  wrote:
> We aren’t talking about fossil ui.  We’re talking about
> 
>  $ f ci -m “closes [12345abc]”

+1
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How to create a ticket link in the wiki?

[Marko Käning]

On 12 May 2016, at 23:22 , Warren Young  wrote:
> The only reason to argue for [12345abc] form is that’s the form artifact IDs 
> take everywhere else in Fossil, most especially including the magic links in 
> checkin comments, which Makrdown wiki links most closely resemble.  Markdown 
> also uses square brackets for links, so it fits.

+1

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Suggestions for list of branches in web-UI

[Marko Käning]

Hi list,

thanks for being so welcomingly responsive to all my posts! :)
I am delighted!!!

What about the issues found in this thread though?

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Workaround for the missing 'squash' command?

[Marko Käning]

Hi Ron,

from what I read about merges in Fossil I had assumed, that they always merge 
in all changes 
changeset after changeset...

On 12 May 2016, at 03:15 , Ron W  wrote:
> I think you are misunderstanding how a merge works in Fossil. The commands:
> fossil update trunk
> fossil merge private
> fossil commit
> will merge the final result of the private branch in to trunk as a single 
> commit. The same result as your diff/patch commands.

But I see now, that I was mistaken in case of a private branch. I think 
fossil’s help page for merge 
should make that difference clear. Could find that on the wiki’s page for 
merging either [1].

Greets,
Marko



[1] http://www.fossil-scm.org/index.html/doc/trunk/www/branching.wiki___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Timestamps in ticket overview pages not shown in local time

[Marko Käning]

Hi Warren,

On 12 May 2016, at 02:05 , Warren Young  wrote:
> … Repeat until expert. :)

nicely said. :)

Will see how much pressure the issues I find/found will be for me and whether 
that
is enough motivation to invest time in this tool.

Well, the least I can do is to post my findings. This might highlight them and
perhaps even trigger someone else to do the work, as there is suddenly a worthy
little project popping up. :)

Thanks for all your replies and caring!

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil timeline on console quirk with ticket titles

[Marko Käning]

Hi Warren,

thanks for the digging! :)

On 12 May 2016, at 01:27 , Warren Young  wrote:
> The problem is on line 1693 of src/manifest.c, if you want to try and fix it. 
>  I believe the proper fix would involve moving these tags into 
> www_print_timeline() in src/timeline.c.

If it bugs me enough I will have a look at it.

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] No progress on "fossil cp"

[Marko Käning]

Hi devs,

as it seems there is no demand of a “cp” command for fossil, really, as nothing
seems to have been done about it in the last 3 years [1].

I guess, it’s the same issue: someone would have to implement it...
No, it’s not me either. ;)

Anyway, still, I consider Fossil a great tool despite it lacking keeping history
when copying files around.

Greets,
Marko



[1] 
http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg09155.html
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How to create a ticket link in the wiki?

[Marko Käning]

On 12 May 2016, at 00:38 , Warren Young <w...@etr-usa.com> wrote:

> On May 11, 2016, at 3:52 PM, Marko Käning <sec001+fos...@posteo.net> wrote:
>> 
>> Referring to tickets on a wiki page like this: [968eb6376d] doesn't work, 
>> where one would have to use [968eb6376d](tktview?name=968eb6376d).
>> 
>> Is this intended, or am I missing something?
> 
> Yes, it’s a known limitation.

I see now.


> To expand on your request, I also think you should be able to say things like
> 
>  …bla bla bla but there is a [plan](1235abc) to fix that.
> 
> in a wiki article that wants to refer to a ticket.

+1
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Timestamps in ticket overview pages not shown in local time

[Marko Käning]

On 12 May 2016, at 00:26 , Warren Young <w...@etr-usa.com> wrote:

> On May 11, 2016, at 3:51 PM, Marko Käning <sec001+fos...@posteo.net> wrote:
>> 
>> Timestamps in ticket overview pages
> 
> I think I see what you mean.  Both the mtime column in /rptview URLs and the 
> User Comments boxes in ticket /info pages use UTC.
> 
> But, if you uncheck Admin > Timeline > Use Universal Coordinated Time (UTC), 
> the Last Modified field in a ticket /info page switches from UTC to local 
> time!
> 
> This is inconsistent and confusing.

+1


> Instead of this being a timeline-specific option, I propose that it affect 
> all times displayed in Fossil UI.  It should perhaps move to Admin > 
> Configuration.

+1


> Then, someone needs to go through the code and add localtime conversions 
> everywhere times are retrieved from the DB, which presumably always stores 
> them in UTC.  I volunteer you. :)

Oh. I never had a look inside Fossil so far… I hope some more proficient with
its code might step in here. :)
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Workaround for the missing 'squash' command?

[Marko Käning]

How to achieve a git'ish squash when merging a (private) branch into trunk?

Is this deliberately missing functionality following fossil's mission to keep 
all history?

Well, especially in case of a _private_ branch it might make sense to have such 
a feature: assume one wants to work locally on something which won’t be touched 
by anyone else for the time being. But when the time comes to make it public 
one might not always want to push the whole history to the central repo.

I figure the only way is to use stg like

$ fossil diff -v -r 5d7b175ba0 >patch.diff

followed by

$ patch http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Feature request: auto-closing of tickets a la Trac

[Marko Käning]

An auto-closing of tickets if the commit comment contains stg like "closed 
[TICKETID]", "closes [TICKETID]", "fixed [TICKETID]", "fixes [TICKETID]", would 
be nice.

This is possible to set up in Trac for instance...
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Feature request: Markdown formatting in ticket comments

[Marko Käning]

It would be nice if ticket comments would use Markdown formatting as well.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] fossil timeline on console quirk with ticket titles

[Marko Käning]

Why does "fossil timeline" show HTML tags around ticket titles, like this: 

Ticket test

???
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to create a ticket link in the wiki?

[Marko Käning]

Referring to tickets on a wiki page like this: [968eb6376d] doesn't work, where 
one would have to use [968eb6376d](tktview?name=968eb6376d).

Is this intended, or am I missing something?

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Timestamps in ticket overview pages not shown in local time

[Marko Käning]

Timestamps in ticket overview pages aren't local time (as in the ticket view 
page), but UTC, which is irritating. Can this be configured differently 
someplace?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Suggestions for list of branches in web-UI

[Marko Käning]

Hi devs,

while using Fossil’s web-UI I noticed some things regarding the display of 
branches.

1) It would be nice, if private branches were marked in /brlist somehow, 
preferably
by introducing a new column entitled “Private”, or stg similar.

2) /brlist should NOT show closed branches (but could have a menu item for 
that). On page /brlist?all the link “Open" leads straight away to /brlist which 
is showing all existing branches, which is INCONSISTENT!

3) The pages for /brlist?all, /brlist?open and /brlist?closed should have the 
same table layout like the /brlist?all page generates it, or are they 
deliberately crippled for some reason?

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Some more default settings for a UI user

[Marko Käning]

I’ve understood now that

$ fossil config push skin

should actually push the clone’s skin to the central repo. :)
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How to migrate a repository's wiki pages to another repo?

[Marko Käning]

Hi Ron,

On 25 Apr 2016, at 09:08 , Ron W  wrote:
> Push will push all content changes, including public check-ins, and wiki, 
> ticket, and tech-note edits.

yeah, but that will only push changes into a repo having a common ancestor, no?
But what about if I want to put parts of a wiki into a completely different 
repo?
There I need an export.
 

> However, the wiki command allows creating, changing and "exporting" wiki 
> pages from the command line.

OK, seeing that now. Well, it doesn’t allow for automatic ex/importing all 
pages, but that could be done with a little bash scripting.

Thanks for the hint!

Greets,
Marko___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Howto change diff output colorisation

[Marko Käning]

Hi again,

On 24.04.2016 19:14, Svyatoslav Mishyn wrote:

You can add into css file
'span.diff*' style attributes, see example:
https://f.juef.tk/fossil-theme-sl/artifact/6601f777f08ef848cc97cc10100f50afac09f1d4?txt=1=215,244


ah, great. That's what I was hoping for.

Thanks,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Feature request: syntax highlighting for file, diff and code block rendering

[Marko Käning]

Hi Svyatoslav,

On 24.04.2016 14:31, Svyatoslav Mishyn wrote:

see: http://www.fossil-scm.org/index.html/wiki?name=shjs


I tried this out, but unfortunately it didn't highlight anything for me.

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Colored output on console

[Marko Käning]

Hi Scott,

On 24.04.2016 18:39, Scott Robison wrote:

I will just observe here that typically red text on a black background
is really hard for me to see. If someone were to add such a thing,
having it be opt in would be appreciated. Different people have
different, of course. I hate color blindness.


how right you are. I also have trouble with red/green deficiency. See my
other post regarding "Howto change diff output colorisation". Khaki hit
against green diff output, impossible to see for my eyes, but clearly
visible for my friend. ;-)

Yes, opt-in and configurable would be the way to go.

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to migrate a repository's wiki pages to another repo?

[Marko Käning]

Hi list,

how can one migrate a repository's wiki pages to another repo?

One could imagine to have some ex/import functionality for wiki pages...

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Howto change diff output colorisation

[Marko Käning]

Hi,

how can one configure the colour scheme of the diff output for a 
specific skin?


For instance the skin "Khaki, No Logo" has a light green background, 
which is very similar
to the light green used for highlighting of added text on the right side 
of a diff output.


It would be advisable to be able to configure the needed color 
definitions for the diff output

together with the residual CSS stuff of a skin.

Right now it seems to be hard-coded somewhere deep in Fossil, since it 
is identical for all

skins.

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Feature request: syntax highlighting for file, diff and code block rendering

[Marko Käning]

Hi Svyatoslav,

On 24 Apr 2016, at 14:31 , Svyatoslav Mishyn <j...@openmailbox.org> wrote:

> (Sun, 24 Apr 12:03) Marko Käning:
>> would be nice if it was possible to get syntax highlighting in the web UI.
> 
> see: http://www.fossil-scm.org/index.html/wiki?name=shjs

that looks interesting.

Thanks, will try.

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Renaming wiki pages

[Marko Käning]

Hi,

are there any plans to implement a “wiki rename” command [1] for fossil?

Greets,
Marko


[1] 
http://stackoverflow.com/questions/22545581/how-can-you-rename-a-wiki-page-in-fossil-scm
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Colored output on console

[Marko Käning]

Hi devs,

it would be great if one could colorise Fossil’s output on the console!

Quite a few times I missed an error or warning message which slipped in between 
of many lines of the usual fossil output on the console.

Red colouring of words like “warning” or “error” would be very helpful there.

The poor man’s solution would at least be to use capital letters and some sort 
of line head along the lines of

> ERROR: blaa
> WARNING: blubb

Right now I can’t send an example of such a easily slipping through message, 
but I can deliver if I come across one again.

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Feature request: syntax highlighting for file, diff and code block rendering

[Marko Käning]

Hi devs,

would be nice if it was possible to get syntax highlighting in the web UI.

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Some more default settings for a UI user

[Marko Käning]

Hi Stephan,

On 24 Apr 2016, at 11:24 , Stephan Beal  wrote:
> i'm not gonna touch those, in the hope that someone with more fingers in the 
> wiki code can say something to them.

no worries, I am very happy about your immediate feedback!

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Some more default settings for a UI user

[Marko Käning]

Hi Stephan,

On 24 Apr 2016, at 10:47 , Stephan Beal  wrote:
> Indeed, it's not intuitive, and i was too tired to get out of bed and back to 
> my full
> keyboard, so was unnecessarily brief ;).

you still responded even when you were supposed to have already nodded off! ;-)

Thanks for all the insights big time. My Fossil wiki’s menu layout is now 
exactly the
way I wanted it by default. Great.

Regarding keeping of more user info I see what you mean. It’s complicated enough
already with all those admin passwords spit out when cloning a remote repo and 
so on…
So, I guess it’s not worth it for now to think in that direction.
Ideally the devs working together find some common decision on the wiki layout
and make the corresponding manipulations once.

Greets,
Marko


P.S.: Any hints for my other two post regarding code blocks and font sizes?

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Search edit field placement

[Marko Käning]

OK, thanks to John I learnt in my other thread [1] that this can be achieved 
via Admin/Skins/Headers.


[1] http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg22970.html
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Some more default settings for a UI user

[Marko Käning]

Hi John,

On 24 Apr 2016, at 01:45 , John P. Rouillard  wrote:
> You're missing what he is saying. He is saying change the Timeline
> (/timeline) link in the menu.

indeed, not hard to miss it. :)

I couldn’t figure out where I could change exactly those links.

Now I see that you’re pointing me to skins:

> When logged in as an admin, go to:
> 
>   Admin/Skins
> 
> You will see text that says:
> 
> A "skin" is a combination of CSS, Header, Footer, and Details 
> 
> Choose Header.

Well, that’s not really intuitive, is it! ;-)

I would have expected something like “Edit menu” or something along that line.


> The html/th1 mix that shows up in the textbox is the top section of
> the pages.
> 
> Search for Timeline and you should see:
> 
>  menulink /timeline Timeline
> 
> Change
>   /timeline
> to
>  '/timeline?n=100'
> 
> and click Apply changes. Now the default value when clicking Timeline
> menu link is to show 100 changes.

Yep, got that now.


> I don't think there is an option to allow logged in users to set those
> sorts of things on a per user basis. AFAIK there is no user data
> stored other than a password. So you would need to figure out how to
> create a user table to store user preferences. There are no custom
> forms for users (i.e. a user equivalent of the admin/tickets
> mechanism), you wouldn't be able to allow the user to edit things
> without some changes to the fossil core code.

OK.


> However once you had that info in the database, IIRC you can use th1 to
> find out who the current user is. Then you can make sql calls into the
> database. So I think in theory you could change/create a user schema
> that holds personalized settings and use th1 to customize the menu
> item.

I see.

Well, I’ve reconfigured the repo’s header now to my linking.

Thanks for the clarification wrt the "Menu Settings" aka Admin/Skins. :)

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Some more default settings for a UI user

[Marko Käning]

On 24 Apr 2016, at 01:07 , Stephan Beal  wrote:

> You need to edit the links in the menus to add parameters for the settings 
> you want. e.g. max is set using n=123.
> 

I know that I can do that, in principle, BUT next time I click the /timeline 
menu link I am back to the default settings for all three parameters, i.e. n=50 
in this case.

BEDTIME NOW! :-)___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Some more default settings for a UI user

[Marko Käning]

Perhaps it is important to note that I am running the current stable version 
1.34,
which I had posted only in my 1st post to the list today:

> I’ve installed fossil’s version 1.34 using MacPorts on OSX. The web UI shows
> this version string:
> 
>   Fossil version [62dcb00e68] 2015-11-02 17:35:44

[ http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg22951.html ]___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Some more default settings for a UI user

[Marko Käning]

My /setup_timeline page gives me these options:

 Allow block-markup in timeline
 Plaintext comments on timelines
 Use Universal Coordinated Time (UTC)
 Per-Item Time Format
 Show version differences by default
 Max timeline comment length

which do not include the 3 additional ones I am seeking for:

> • Timeline view:
> - Type of entries (e.g. only check-ins)
> - Max. 
> - With/Without Files
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Some more default settings for a UI user

[Marko Käning]

Hi Stephan,

On 24 Apr 2016, at 00:49 , Stephan Beal  wrote:
> All 3 of those options are there, but i am in bed and won't be up for 
> (ideally) another 10 hours, so i am hoping someone else will point them out 
> ;). Help is not in the default menu because it is, in practice, rarely used. 
> Feel free to add it to yours.
> 
ok, thanks for reassuring. I will search on a bit and thus wish you a good 
night.

Bye,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Some more default settings for a UI user

[Marko Käning]

On 24 Apr 2016, at 00:25 , Stephan Beal  wrote:
> Ps: see the /help page for the various /timeline options.
> 
Well, this allows a couple of settings, yes, but not the three I asked for:

>  • Timeline view:
>  - Type of entries (e.g. only check-ins)
>  - Max.
>  - With/Without Files


For the tree view there’s also nothing specific for the menu structure to be 
found:

>  • Files view:
>  - would be nice to be able to set it e.g. by default to tree-view.


Thanks for the pointer to the /help page. Would be nice to have that link 
already in 
Fossil's vanilla version of the UI, as it is a great overview of all the 
commands.___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Some more default settings for a UI user

[Marko Käning]

Hi Sephan,

On 24 Apr 2016, at 00:23 , Stephan Beal  wrote:
> You can achieve all of that by changing the appropriate menu entries/links 
> via the setup page. If
> 
I am puzzled, as I can’t seem to find the correct setup page which makes the 
wiki’s menu links 
available for configuration.

Greets,
Marko


P.S.: Running the web UI via “fossil ui” here, but I guess that shouldn’t make 
any difference.___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Some more default settings for a UI user

[Marko Käning]

Hi,

it would be nice to have some default settings definable for a user:

 • Timeline view:
 - Type of entries (e.g. only check-ins)
 - Max. 
 - With/Without Files

 • Files view:
 - would be nice to be able to set it e.g. by default to tree-view.

This would be probably ideally configurable via Admin/Configuration.

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Code blocks with more vertical space possible?

[Marko Käning]

Hi,

is it possible to define code-blocks which

  1) have extra vertical space for better separation
 in paragraphs or stg like list items?

  2) have perhaps even a frame around them?


I guess this all could be achieved by some CSS magic,
but I think it would be nice to have that as standard
behaviour. 

E.g. in "Review Board"’s or GitHub’s wiki syntax one
can use three apostrophes
```
 to mark a code block (like this)
```
which will then be rendered with more vertical space
and in case of RB also with a box around it.


Perhaps this is also possible in Fossil’s wiki, but
my tries to get something similar using Fossil’s
Markdown syntax weren’t successful up to now.

Any pointers?

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil's ticket edit dialog page seems broken, since the ticket's comment is not displayed at all

[Marko Käning]

On 23 Apr 2016, at 23:39 , Stephan Beal  wrote:
> It can only amend new info to a ticket, not replace anything. 

OK, that makes sense, yes. Thanks for the pointer!

I see now that it also says “Append Remark with format” in the edit dialog page 
for the field which I thought should have contained the comment.

That’s fine then.___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Some weird font sizes in wiki on OSX

[Marko Käning]

Hi devs,

why do the font sizes in fossil's wiki rendering (for code snippets)
aren't really nicely matching the text flow?

 If I want to render a code snippet with apostrophes like `this snippet`,
 then the font used for text “this snippet” would be only 75% the size I’d
 expect it to have to match the surrounding font.

Is this only an issue on OSX (happens on up-to-date Safari and Firefox)?

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Search edit field placement

[Marko Käning]

Hi devs,

if the search feature is enabled the [Wiki](/wiki) and [Tickets](/ticket) views
show at first the search edit field instead of the list of available wiki/ticket
overview pages, which would make more sense - so I believe...

One could also think about having the search edit field together with the
corresponding overview on those pages, instead of being forced to click around
again and again.

Just a suggestion.

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Fossil's ticket edit dialog page seems broken, since the ticket's comment is not displayed at all

[Marko Käning]

Hi folks,

---

>First of all< I want to say that I am delighted with this SCM system,
after having used CVS, SVN, Mercurial and Git for quite some time...

I’ve liked to use Mercurial with the b extension to keep my bugs in
source control together with the code...

... but fossil is way better! There’s not only a ticketing system, but
also a wiki and lots of other goodies!

!!! Great stuff !!!

===


I’ve installed fossil’s version 1.34 using MacPorts on OSX. The web UI shows
this version string:

Fossil version [62dcb00e68] 2015-11-02 17:35:44

---

And now to my first issue:

  For some reason fossil's ticket edit dialog page (/tktedit?name=ARTIFACTID)
  seems broken, as it doesn't show the actual ticket comment which had been
  entered previously by its creator.

  However, the information has been stored in the database, as it gets
  correctly displayed using the ticket view dialog (/tktview?name=ARTIFACTID)!

  Also clicking the “Preview” button does not miraculously show the ticket
  comment in the "Description Preview”.

So, what’s this about?

Could it be that the edit ticket page’s code in /tktsetup_editpage got borked?
I haven’t touched that at all up to now. It’s all in virgin state.

Ideas?

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How to file a ticket on fossil-scm.org?

[Marko Käning]

Hi Richard,

ok, fair enough, I will use the mailing list then. Thanks!!

Greets,
Marko

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to file a ticket on fossil-scm.org?

[Marko Käning]

Hi,

I am new to fossil and thought that I could file a ticket at fossil’s ticket 
tracker.

I logged on as “anonymous”, as suggested by the wiki, but there is no button 
for creating a new ticket.

What should I do instead?

Greets,
Marko
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users