From 0d2769f4bae4e44e20c6cc5d9f9b3dec3d5effd2 Mon Sep 17 00:00:00 2001 From: "http://seanh.myopenid.com/" Date: Wed, 1 Apr 2009 07:26:06 -0400 Subject: --- doc/forum/How_does_ikiwiki_remember_times__63__.mdwn | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/How_does_ikiwiki_remember_times__63__.mdwn (limited to 'doc/forum') diff --git a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn new file mode 100644 index 000000000..c23f0b100 --- /dev/null +++ b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn @@ -0,0 +1,10 @@ +This is similar to the last post in this forum. I want to know exactly how ikiwiki remembers the times associated with pages, especially when using it for blogging, so I know whether I can trust it or not. From that last thread, I think what ikiwiki does is this: + +* The created time of a file is when that file was first committed into the versioning repository (in my case git) +* The modified time of a file is what that file was last updated in the repository + +And with a blog, by default, the posts are ordered by creation time, although an option can order them by modified time. + +Okay. So this should mean that the times are safe if, for example, I delete my working copy and then clone another one from the bare git repository, or otherwise mess up the creation times and mtimes stored as file metadata on the filesystem. + +Do I have it right? -- cgit v1.2.3 From cb09a4eb875f3c609d0d283d08c64643ee3ccfe2 Mon Sep 17 00:00:00 2001 From: Jon Dowland Date: Wed, 1 Apr 2009 12:31:33 +0100 Subject: response --- doc/forum/managing_todo_lists.mdwn | 3 +++ 1 file changed, 3 insertions(+) (limited to 'doc/forum') diff --git a/doc/forum/managing_todo_lists.mdwn b/doc/forum/managing_todo_lists.mdwn index b4bbac255..0a69af805 100644 --- a/doc/forum/managing_todo_lists.mdwn +++ b/doc/forum/managing_todo_lists.mdwn @@ -39,3 +39,6 @@ sure how to handle embeds or challenges from the CGI such as a login challenge >> thanks - I'll give it a look. I spent a few hours writing some javascript to manipulate a ul/li DOM tree in an outliner-fashion the other day. I might be able to join the puzzle pieces together sometime. [[Jon]] a solution for this could be similar to a solution for [[todo/structured page data]], as todo lists are definitely a form of structured data. (in both cases, the page's current content is rendered into a html form, whose result is then saved as the page's new contents) --[[chrysn]] + +> Thanks for the link: yup, there's definitely some common ground there. +> -- [[Jon]] -- cgit v1.2.3 From 3496eac54b05afd2c45c225e788a928bf4289704 Mon Sep 17 00:00:00 2001 From: Jon Dowland Date: Wed, 1 Apr 2009 12:33:33 +0100 Subject: move managing todo lists to 'todo' section --- doc/forum/managing_todo_lists.mdwn | 44 ------------------------------ doc/todo/managing_todo_lists.mdwn | 55 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 55 insertions(+), 44 deletions(-) delete mode 100644 doc/forum/managing_todo_lists.mdwn create mode 100644 doc/todo/managing_todo_lists.mdwn (limited to 'doc/forum') diff --git a/doc/forum/managing_todo_lists.mdwn b/doc/forum/managing_todo_lists.mdwn deleted file mode 100644 index 0a69af805..000000000 --- a/doc/forum/managing_todo_lists.mdwn +++ /dev/null @@ -1,44 +0,0 @@ -I keep some TODO lists on ikiwiki pages. I'm half-tempted to write a plugin -to make ticking items off and adding items easier via the web interface. I'm -aware though that this is not really what ikiwiki is designed for. Would -anyone else find this useful? -- [[users/jon]] - ----- - -My subsequent thoughts about how to approach this are two-fold. - -Firstly, a filetype for todo lists, probably OPML, but I haven't looked to see -if there is something more suitable. A plugin that converts this source into a -traditional page output, i.e. a DOM tree of ul or ol and li elements. - -Secondly, some magic javascript to make editing the list via the web page -more interactive: add items, strike items out, reorder items etc., without -round-tripping to the cgi for each operation. - -Finally, a mechanism whereby the changes made to the page live can be -committed back to the repository: - - * ...perhaps the input → output conversion is reversible, and the HTML DOM - representing the list can be transformed back into the source and submitted - to the cgi like a regular edit: issues include the result of other - postprocessing: templates, wikilinks, etc. - * perhaps an embedded copy of the source is included in the output and the - javascript operates on that in tandem with the static copy - * perhaps the "output" is generated live by the JS at view time (with maybe - a plugin-generated rendered output for non JS environments) - -I envisage a button called "commit changes" appearing once some changes are -made that submits the changes to the CGI, perhaps via a back channel. I'm not -sure how to handle embeds or challenges from the CGI such as a login challenge -(maybe the back channel would not be necessary in the first cut). - -> You might look at the [[plugins/hnb]] plugin. HNB supports checklists. -> There's not a fancy web interface, but the hnb command-line program can -> be used to edit them. --[[Joey]] - ->> thanks - I'll give it a look. I spent a few hours writing some javascript to manipulate a ul/li DOM tree in an outliner-fashion the other day. I might be able to join the puzzle pieces together sometime. [[Jon]] - -a solution for this could be similar to a solution for [[todo/structured page data]], as todo lists are definitely a form of structured data. (in both cases, the page's current content is rendered into a html form, whose result is then saved as the page's new contents) --[[chrysn]] - -> Thanks for the link: yup, there's definitely some common ground there. -> -- [[Jon]] diff --git a/doc/todo/managing_todo_lists.mdwn b/doc/todo/managing_todo_lists.mdwn new file mode 100644 index 000000000..846f2a4af --- /dev/null +++ b/doc/todo/managing_todo_lists.mdwn @@ -0,0 +1,55 @@ +I keep some TODO lists on ikiwiki pages. I'm half-tempted to write a plugin +to make ticking items off and adding items easier via the web interface. I'm +aware though that this is not really what ikiwiki is designed for. Would +anyone else find this useful? -- [[users/jon]] + +---- + +My subsequent thoughts about how to approach this are two-fold. + +Firstly, a filetype for todo lists, probably OPML, but I haven't looked to see +if there is something more suitable. A plugin that converts this source into a +traditional page output, i.e. a DOM tree of ul or ol and li elements. + +Secondly, some magic javascript to make editing the list via the web page +more interactive: add items, strike items out, reorder items etc., without +round-tripping to the cgi for each operation. + +Finally, a mechanism whereby the changes made to the page live can be +committed back to the repository: + + * ...perhaps the input → output conversion is reversible, and the HTML DOM + representing the list can be transformed back into the source and submitted + to the cgi like a regular edit: issues include the result of other + postprocessing: templates, wikilinks, etc. + * perhaps an embedded copy of the source is included in the output and the + javascript operates on that in tandem with the static copy + * perhaps the "output" is generated live by the JS at view time (with maybe + a plugin-generated rendered output for non JS environments) + +I envisage a button called "commit changes" appearing once some changes are +made that submits the changes to the CGI, perhaps via a back channel. I'm not +sure how to handle embeds or challenges from the CGI such as a login challenge +(maybe the back channel would not be necessary in the first cut). + +> You might look at the [[plugins/hnb]] plugin. HNB supports checklists. +> There's not a fancy web interface, but the hnb command-line program can +> be used to edit them. --[[Joey]] + +>> thanks - I'll give it a look. I spent a few hours writing some javascript to manipulate a ul/li DOM tree in an outliner-fashion the other day. I might be able to join the puzzle pieces together sometime. [[Jon]] + +a solution for this could be similar to a solution for [[todo/structured page data]], as todo lists are definitely a form of structured data. (in both cases, the page's current content is rendered into a html form, whose result is then saved as the page's new contents) --[[chrysn]] + +> Thanks for the link: yup, there's definitely some common ground there. +> -- [[Jon]] + +---- + +I had a little spare time in a conference recently so I hacked on this. I +managed to get something working with anonok, a "markup format" that was +essentially just UL and LI elements and some javascript. I'll try and get an +example up of that soon (and publish the code). There's still quite a lot of +work necessary, but it's more than an idle thought at least! + +I've moved this page under the [[todo]] heirarchy as I'm actually working on +this now. -- [[Jon]] -- cgit v1.2.3 From 9a7e8096c09efdb7d36656ad6e4aae4dec49a39b Mon Sep 17 00:00:00 2001 From: Jon Dowland Date: Wed, 1 Apr 2009 13:30:20 +0100 Subject: Revert "move managing todo lists to 'todo' section" This reverts commit 3496eac54b05afd2c45c225e788a928bf4289704. Rather than move the existing forum topic (and confuse anyone who expected to find it there) I will create a new TODO item, structured more traditionally. --- doc/forum/managing_todo_lists.mdwn | 44 ++++++++++++++++++++++++++++++ doc/todo/managing_todo_lists.mdwn | 55 -------------------------------------- 2 files changed, 44 insertions(+), 55 deletions(-) create mode 100644 doc/forum/managing_todo_lists.mdwn delete mode 100644 doc/todo/managing_todo_lists.mdwn (limited to 'doc/forum') diff --git a/doc/forum/managing_todo_lists.mdwn b/doc/forum/managing_todo_lists.mdwn new file mode 100644 index 000000000..0a69af805 --- /dev/null +++ b/doc/forum/managing_todo_lists.mdwn @@ -0,0 +1,44 @@ +I keep some TODO lists on ikiwiki pages. I'm half-tempted to write a plugin +to make ticking items off and adding items easier via the web interface. I'm +aware though that this is not really what ikiwiki is designed for. Would +anyone else find this useful? -- [[users/jon]] + +---- + +My subsequent thoughts about how to approach this are two-fold. + +Firstly, a filetype for todo lists, probably OPML, but I haven't looked to see +if there is something more suitable. A plugin that converts this source into a +traditional page output, i.e. a DOM tree of ul or ol and li elements. + +Secondly, some magic javascript to make editing the list via the web page +more interactive: add items, strike items out, reorder items etc., without +round-tripping to the cgi for each operation. + +Finally, a mechanism whereby the changes made to the page live can be +committed back to the repository: + + * ...perhaps the input → output conversion is reversible, and the HTML DOM + representing the list can be transformed back into the source and submitted + to the cgi like a regular edit: issues include the result of other + postprocessing: templates, wikilinks, etc. + * perhaps an embedded copy of the source is included in the output and the + javascript operates on that in tandem with the static copy + * perhaps the "output" is generated live by the JS at view time (with maybe + a plugin-generated rendered output for non JS environments) + +I envisage a button called "commit changes" appearing once some changes are +made that submits the changes to the CGI, perhaps via a back channel. I'm not +sure how to handle embeds or challenges from the CGI such as a login challenge +(maybe the back channel would not be necessary in the first cut). + +> You might look at the [[plugins/hnb]] plugin. HNB supports checklists. +> There's not a fancy web interface, but the hnb command-line program can +> be used to edit them. --[[Joey]] + +>> thanks - I'll give it a look. I spent a few hours writing some javascript to manipulate a ul/li DOM tree in an outliner-fashion the other day. I might be able to join the puzzle pieces together sometime. [[Jon]] + +a solution for this could be similar to a solution for [[todo/structured page data]], as todo lists are definitely a form of structured data. (in both cases, the page's current content is rendered into a html form, whose result is then saved as the page's new contents) --[[chrysn]] + +> Thanks for the link: yup, there's definitely some common ground there. +> -- [[Jon]] diff --git a/doc/todo/managing_todo_lists.mdwn b/doc/todo/managing_todo_lists.mdwn deleted file mode 100644 index 846f2a4af..000000000 --- a/doc/todo/managing_todo_lists.mdwn +++ /dev/null @@ -1,55 +0,0 @@ -I keep some TODO lists on ikiwiki pages. I'm half-tempted to write a plugin -to make ticking items off and adding items easier via the web interface. I'm -aware though that this is not really what ikiwiki is designed for. Would -anyone else find this useful? -- [[users/jon]] - ----- - -My subsequent thoughts about how to approach this are two-fold. - -Firstly, a filetype for todo lists, probably OPML, but I haven't looked to see -if there is something more suitable. A plugin that converts this source into a -traditional page output, i.e. a DOM tree of ul or ol and li elements. - -Secondly, some magic javascript to make editing the list via the web page -more interactive: add items, strike items out, reorder items etc., without -round-tripping to the cgi for each operation. - -Finally, a mechanism whereby the changes made to the page live can be -committed back to the repository: - - * ...perhaps the input → output conversion is reversible, and the HTML DOM - representing the list can be transformed back into the source and submitted - to the cgi like a regular edit: issues include the result of other - postprocessing: templates, wikilinks, etc. - * perhaps an embedded copy of the source is included in the output and the - javascript operates on that in tandem with the static copy - * perhaps the "output" is generated live by the JS at view time (with maybe - a plugin-generated rendered output for non JS environments) - -I envisage a button called "commit changes" appearing once some changes are -made that submits the changes to the CGI, perhaps via a back channel. I'm not -sure how to handle embeds or challenges from the CGI such as a login challenge -(maybe the back channel would not be necessary in the first cut). - -> You might look at the [[plugins/hnb]] plugin. HNB supports checklists. -> There's not a fancy web interface, but the hnb command-line program can -> be used to edit them. --[[Joey]] - ->> thanks - I'll give it a look. I spent a few hours writing some javascript to manipulate a ul/li DOM tree in an outliner-fashion the other day. I might be able to join the puzzle pieces together sometime. [[Jon]] - -a solution for this could be similar to a solution for [[todo/structured page data]], as todo lists are definitely a form of structured data. (in both cases, the page's current content is rendered into a html form, whose result is then saved as the page's new contents) --[[chrysn]] - -> Thanks for the link: yup, there's definitely some common ground there. -> -- [[Jon]] - ----- - -I had a little spare time in a conference recently so I hacked on this. I -managed to get something working with anonok, a "markup format" that was -essentially just UL and LI elements and some javascript. I'll try and get an -example up of that soon (and publish the code). There's still quite a lot of -work necessary, but it's more than an idle thought at least! - -I've moved this page under the [[todo]] heirarchy as I'm actually working on -this now. -- [[Jon]] -- cgit v1.2.3 From 16e951065e43cd3217f77541184b2d07492a1e70 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 1 Apr 2009 19:32:02 -0400 Subject: response --- doc/forum/How_does_ikiwiki_remember_times__63__.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'doc/forum') diff --git a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn index c23f0b100..ff588fe6c 100644 --- a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn +++ b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn @@ -1,10 +1,26 @@ This is similar to the last post in this forum. I want to know exactly how ikiwiki remembers the times associated with pages, especially when using it for blogging, so I know whether I can trust it or not. From that last thread, I think what ikiwiki does is this: * The created time of a file is when that file was first committed into the versioning repository (in my case git) + + > If `--getctime` it used, yes. In normal operation, when new files + > are added, ikiwiki sets the creation time to the ctime of the file + > on disk, rather than bothering to ask the VCS. --[[Joey]] + * The modified time of a file is what that file was last updated in the repository + > Almost right, the modified time is actually taken from the + > modification time of the file in disk. --[[Joey]] + And with a blog, by default, the posts are ordered by creation time, although an option can order them by modified time. Okay. So this should mean that the times are safe if, for example, I delete my working copy and then clone another one from the bare git repository, or otherwise mess up the creation times and mtimes stored as file metadata on the filesystem. Do I have it right? + +> Some VCS, like git, set the file mtimes to the current time +> when making a new checkout, so they will be lost if you do that. +> The creation times can be retrived using the `--getctime` option. +> I suppose it might be nice if there were a `--getmtime` that pulled +> true modification times out of the VCS, but I haven't found it a big +> deal in practice for the last modification times to be updated to the +> current time when rebuilding a wiki like this. --[[Joey]] -- cgit v1.2.3 From f8f9cc46b89bab5bc9c0b27e1832a5699c2a3003 Mon Sep 17 00:00:00 2001 From: "http://seanh.myopenid.com/" Date: Thu, 2 Apr 2009 07:44:33 -0400 Subject: --- .../How_does_ikiwiki_remember_times__63__.mdwn | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) (limited to 'doc/forum') diff --git a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn index ff588fe6c..f199b0f3b 100644 --- a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn +++ b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn @@ -24,3 +24,28 @@ Do I have it right? > true modification times out of the VCS, but I haven't found it a big > deal in practice for the last modification times to be updated to the > current time when rebuilding a wiki like this. --[[Joey]] +> +> > Thanks for the clarification. I ran some tests of my own to make sure I understand it right, and I'm satisfied +> > that the order of posts in my blog can be retrieved from the VCS using the `--getctime` option, at least if I +> > choose to order my posts by creation time rather than modification time. But I now know that I can't rely on +> > page modification times in ikiwiki as these can be lost permanently. +> > +> > I would suggest that there should at least be a `--getmtime` option like you describe, and perhaps that +> > `--getctime` and `--getmtime` be _on by default_. In my opinion the creation times and modification times of +> > pages in ikiwiki are part of the user's content and are important to protect, because the user may be relying +> > on them, especially if they use blogging or lists of recently modified pages, etc. Right now the modification +> > times can be lost permanently. +> > +> > Is there a typo in the description of `--getctime` in the man page? +> > +> > > --getctime +> > > Pull **last changed time** for each new page out of the revision +> > > control system. This rarely used option provides a way to get +> > > the real creation times of items in weblogs, such as when build‐ +> > > ing a wiki from a new Subversion checkout. It is unoptimised and +> > > quite slow. It is best used with --rebuild, to force ikiwiki to +> > > get the ctime for all pages. +> > +> > Surely it is not the _last changed time_ but the _first seen time_ of each page that is pulled out of the VCS? +> > If the aim is to get the real creation times of items in weblogs, then the last times that the items were +> > changed in the VCS is not going to help. -- [[seanh]] -- cgit v1.2.3 From 5c7c3646d848301017a0a588af1b5711133df2ec Mon Sep 17 00:00:00 2001 From: "http://seanh.myopenid.com/" Date: Thu, 2 Apr 2009 07:46:04 -0400 Subject: --- doc/forum/seanh.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/forum/seanh.mdwn (limited to 'doc/forum') diff --git a/doc/forum/seanh.mdwn b/doc/forum/seanh.mdwn new file mode 100644 index 000000000..d093c2f32 --- /dev/null +++ b/doc/forum/seanh.mdwn @@ -0,0 +1 @@ +seanh is an ikiwiki user. -- cgit v1.2.3 From 597009e8bc3c2359045614f273f065a5de942a04 Mon Sep 17 00:00:00 2001 From: Jon Dowland Date: Thu, 2 Apr 2009 13:15:30 +0100 Subject: use meta date='foo' --- doc/forum/How_does_ikiwiki_remember_times__63__.mdwn | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'doc/forum') diff --git a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn index f199b0f3b..067aa0c09 100644 --- a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn +++ b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn @@ -49,3 +49,7 @@ Do I have it right? > > Surely it is not the _last changed time_ but the _first seen time_ of each page that is pulled out of the VCS? > > If the aim is to get the real creation times of items in weblogs, then the last times that the items were > > changed in the VCS is not going to help. -- [[seanh]] + +> > > If you want to preserve the date of a page, the best way to do it is to +> > > use [[ikiwiki/directive/meta]] date="foo". This will survive checkouts, +> > > VCS migrations, etc. -- [[Jon]] -- cgit v1.2.3 From a70a8912362a1c746e1d802c5b3dd2b0c92a9d49 Mon Sep 17 00:00:00 2001 From: Jon Dowland Date: Thu, 2 Apr 2009 13:17:59 +0100 Subject: move seanh's user page from forum/ to user/ I hope you don't mind, It seemed fairly clear this was mistakenly under forum/. --- doc/forum/seanh.mdwn | 1 - doc/users/seanh.mdwn | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) delete mode 100644 doc/forum/seanh.mdwn create mode 100644 doc/users/seanh.mdwn (limited to 'doc/forum') diff --git a/doc/forum/seanh.mdwn b/doc/forum/seanh.mdwn deleted file mode 100644 index d093c2f32..000000000 --- a/doc/forum/seanh.mdwn +++ /dev/null @@ -1 +0,0 @@ -seanh is an ikiwiki user. diff --git a/doc/users/seanh.mdwn b/doc/users/seanh.mdwn new file mode 100644 index 000000000..d093c2f32 --- /dev/null +++ b/doc/users/seanh.mdwn @@ -0,0 +1 @@ +seanh is an ikiwiki user. -- cgit v1.2.3 From 582312e91cb3e2c8313da6bbda735566a05c7677 Mon Sep 17 00:00:00 2001 From: "http://seanh.myopenid.com/" Date: Thu, 2 Apr 2009 09:07:53 -0400 Subject: --- ...w_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn (limited to 'doc/forum') diff --git a/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn b/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn new file mode 100644 index 000000000..b5e8a14dd --- /dev/null +++ b/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn @@ -0,0 +1,8 @@ +I'm getting a number of errors like this when running ikiwiki: + + utf8 "\xA2" does not map to Unicode at /usr/local/share/perl/5.10.0/IkiWiki.pm line 739, <$in> chunk 1. + +I think it's because some of my files contain non-utf8, non-unicode, or somehow bad characters in them, probably fancy quotes and the like that have been copy-and-pasted from my web browser. The problem is that I have hundreds of files, I transferred them all over from pyblosxom to ikiwiki at once, and the error message doesn't tell me which file the error comes from. How can I fix this? + +Thanks +-- seanh -- cgit v1.2.3 From a24a669cabb9475e2e4bddb588ef15b51d73d376 Mon Sep 17 00:00:00 2001 From: "http://seanh.myopenid.com/" Date: Thu, 2 Apr 2009 09:53:06 -0400 Subject: --- doc/forum/How_does_ikiwiki_remember_times__63__.mdwn | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'doc/forum') diff --git a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn index 067aa0c09..0e771cd0d 100644 --- a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn +++ b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn @@ -53,3 +53,8 @@ Do I have it right? > > > If you want to preserve the date of a page, the best way to do it is to > > > use [[ikiwiki/directive/meta]] date="foo". This will survive checkouts, > > > VCS migrations, etc. -- [[Jon]] +> > > +> > > > That's a good tip Jon. That would also survive renaming a page by renaming its mdwn file, which would +> > > > normally lose the times also. (And in that case I think both times are irretrievable, even by +> > > > `--getctime`). I might start using a simple script to make blog posts that creates a file for +> > > > me, puts today's date in the file as a meta, and opens the file in my editor. -- [[seanh]] -- cgit v1.2.3 From e215d023e6e8ca672a77220f3e39904b28fba296 Mon Sep 17 00:00:00 2001 From: Jon Dowland Date: Thu, 2 Apr 2009 16:15:41 +0100 Subject: example script --- .../How_does_ikiwiki_remember_times__63__.mdwn | 28 ++++++++++++++++++++++ 1 file changed, 28 insertions(+) (limited to 'doc/forum') diff --git a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn index 0e771cd0d..3da37f3d4 100644 --- a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn +++ b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn @@ -58,3 +58,31 @@ Do I have it right? > > > > normally lose the times also. (And in that case I think both times are irretrievable, even by > > > > `--getctime`). I might start using a simple script to make blog posts that creates a file for > > > > me, puts today's date in the file as a meta, and opens the file in my editor. -- [[seanh]] + +>>>>> I use a script that does that and also sets up templates and tags +>>>>> for a new item: + + #!/bin/sh + set -u + set -e + + if [ $# -ne 1 ]; then + echo usage: $0 pagename >&2 + exit 1 + fi + + pagename="$1" + + if [ -e "$pagename" ]; then + echo error: "$pagename" exists >&2 + exit 1 + fi + + date=$(date) + echo '[[!template id=draft]]' >> "$pagename" + echo "[[!meta date=\"$date\"]]" >> "$pagename" + echo "[[!tag draft]]" >> "$pagename" + git add "$pagename" + $EDITOR "$pagename" + +>>>>> -- [[Jon]] -- cgit v1.2.3 From fb4f21c438d05e0a171fc3b2cc74636687a3f1a5 Mon Sep 17 00:00:00 2001 From: Jon Dowland Date: Thu, 2 Apr 2009 16:15:53 +0100 Subject: add some escapes --- doc/forum/How_does_ikiwiki_remember_times__63__.mdwn | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/forum') diff --git a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn index 3da37f3d4..d492961ac 100644 --- a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn +++ b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn @@ -79,9 +79,9 @@ Do I have it right? fi date=$(date) - echo '[[!template id=draft]]' >> "$pagename" - echo "[[!meta date=\"$date\"]]" >> "$pagename" - echo "[[!tag draft]]" >> "$pagename" + echo '\[[!template id=draft]]' >> "$pagename" + echo "\[[!meta date=\"$date\"]]" >> "$pagename" + echo "\[[!tag draft]]" >> "$pagename" git add "$pagename" $EDITOR "$pagename" -- cgit v1.2.3 From eec38e8eeb63f6a93c60fc7b9e7e23b28e3b13e8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 3 Apr 2009 14:28:15 -0400 Subject: fix typo in --getctime description --- doc/forum/How_does_ikiwiki_remember_times__63__.mdwn | 1 + doc/usage.mdwn | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) (limited to 'doc/forum') diff --git a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn index d492961ac..5522cbf45 100644 --- a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn +++ b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn @@ -49,6 +49,7 @@ Do I have it right? > > Surely it is not the _last changed time_ but the _first seen time_ of each page that is pulled out of the VCS? > > If the aim is to get the real creation times of items in weblogs, then the last times that the items were > > changed in the VCS is not going to help. -- [[seanh]] +>>> Typo, fixed. --[[Joey]] > > > If you want to preserve the date of a page, the best way to do it is to > > > use [[ikiwiki/directive/meta]] date="foo". This will survive checkouts, diff --git a/doc/usage.mdwn b/doc/usage.mdwn index e2fe85ff6..0c618de5c 100644 --- a/doc/usage.mdwn +++ b/doc/usage.mdwn @@ -308,10 +308,10 @@ also be configured using a setup file. * --getctime - Pull last changed time for each new page out of the revision control + Pull creation time for each new page out of the revision control system. This rarely used option provides a way to get the real creation times of items in weblogs, such as when building a wiki from a new - Subversion checkout. It is unoptimised and quite slow. It is best used + VCS checkout. It is unoptimised and quite slow. It is best used with --rebuild, to force ikiwiki to get the ctime for all pages. * --set var=value -- cgit v1.2.3 From 90da6cc05ca92ab856b21eff1a35cfb7d84db5f6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 3 Apr 2009 14:37:53 -0400 Subject: response --- ...fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'doc/forum') diff --git a/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn b/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn index b5e8a14dd..0b3895357 100644 --- a/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn +++ b/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn @@ -6,3 +6,15 @@ I think it's because some of my files contain non-utf8, non-unicode, or somehow Thanks -- seanh + +> Unfortunatly, these messages are logged by perl so there's no way to add +> a filename to them. +> +> If you run the build in --verbose mode, you should see which page ikiwiki +> is working on, and unless it inlines some other page, you can be pretty +> sure that page contains invalid utf-8 if the message is then printed. +> +> Another option is to use the `isutf8` program from +> moreutils](http://kitenet.net/~joey/code/moreutils/), +> and run it on each file, it will tell you the line number +> and character position that is invalid. --[[Joey]] -- cgit v1.2.3 From 5ca2e2208c1c141b579f8103a3d0432a6c33fe8f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 4 Apr 2009 18:39:55 -0400 Subject: update --- doc/forum/Darcs_as_the_RCS___63__.mdwn | 2 ++ 1 file changed, 2 insertions(+) (limited to 'doc/forum') diff --git a/doc/forum/Darcs_as_the_RCS___63__.mdwn b/doc/forum/Darcs_as_the_RCS___63__.mdwn index 2635690f7..9664240ee 100644 --- a/doc/forum/Darcs_as_the_RCS___63__.mdwn +++ b/doc/forum/Darcs_as_the_RCS___63__.mdwn @@ -9,3 +9,5 @@ What should I put in the configuration file to use darcs ? > Darcs is not yet supported. It's being [[worked_on|todo/darcs]]. > > That's good news for me then ! Thank you. + +>>> Better news: It will be in version 2.10. --[[Joey]] -- cgit v1.2.3