Mercurial > hg > Blog
changeset 97:e99db3bc53c1
Updates for pelican 4.2.0, publish the blog as HTTPS instead of HTTP
line wrap: on
line diff
--- a/content/Eclipse/validating-xml-documents.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/Eclipse/validating-xml-documents.md Thu Dec 19 09:31:57 2019 +0100 @@ -13,10 +13,10 @@ With a bit of googling I found out that the key to success is the proper definition of namespaces and their URLs. In the normal case (as with the spring schema) the schema file is published on the net and can be downloaded by the XML parser. Publishing the schema you're just developing each time you make a change is cumbersome so I figured there must be a better way. The solution is to declare your schema in Eclipse's **XML catalog**. Go to `Preferences` -> `Web and XML` -> `XML Catalog` (assuming that you have WTP installed) and declare a user entry for the schema you're currently developing. Your Eclipse XML Catalog should look similar to this (just with more entries): - + Unfortunately, the validation and autocompletion still does not work if you don't use a little trick to make things work. XML files can be associated to their schema in two ways: either you point the schemaLocation to the full URL where the schema file can be downloaded or you specify a XML catalog key. When not being processed by Eclipse's XML editor the document should still work. We don't publish an XML catalog for mule but if you use a little trick you can still make the editor validate correctly. As XML catalog key specify the full URL to the schema like this: - + The XML catalog validation seems to have preference over the download of schemas from the web. So Eclipse sees the "URL" as catalog key and validates against your schema on disk. When running as part of mule, the schema will be validated by spring's xml parser which uses other means of getting the schema file.
--- a/content/Linux/file-manager.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/Linux/file-manager.md Thu Dec 19 09:31:57 2019 +0100 @@ -2,7 +2,7 @@ Date: 2016-02-10 Lang: en - + On my [Gentoo](http://www.gentoo.org/) machine the "Show in System Explorer" menu item did not work on Eclipse. I kept getting this error message:
--- a/content/Smartphone/odin-on-virtualbox.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/Smartphone/odin-on-virtualbox.md Thu Dec 19 09:31:57 2019 +0100 @@ -9,5 +9,5 @@ * download the Windows drivers for Samsung Galaxy S (e.g. from Softpedia) and install * shut down Windows * connect the Samsung Galaxy via USB -* in the VirtualBox Manager define an USB filter<br> +* in the VirtualBox Manager define an USB filter<br> * power up VirtualBox and use Odin to flash
--- a/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/0.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/0.md Thu Dec 19 09:31:57 2019 +0100 @@ -1,4 +1,3 @@ -Title: Author: jokraehe Date: 2014-02-12 21:30:49
--- a/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/1.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/1.md Thu Dec 19 09:31:57 2019 +0100 @@ -1,6 +1,5 @@ -Title: Author: Dirk Olmes Date: 2014-02-15 16:30:00 -ReplyTo: 0md +ReplyTo: 0.md I dug to the root cause of the issue back after I wrote the blog post but didn't find the time to do a proper comparison of ikec's behaviour on the pi vs on my regular Linux machine. Long story short, it was the code that parses the config file. On the pi it doesn't proplerly detect the last entry in the file - or EOF, I don't remember the details. The workaround was to add an empty line to the end of the config file.
--- a/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/2.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/2.md Thu Dec 19 09:31:57 2019 +0100 @@ -1,4 +1,3 @@ -Title: Author: Nkolay Dimitrov Date: 2015-10-31 22:13:37
--- a/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/3.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/3.md Thu Dec 19 09:31:57 2019 +0100 @@ -1,4 +1,3 @@ -Title: Author: John de Sousa Date: 2017-10-26 14:04:46
--- a/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/4.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/4.md Thu Dec 19 09:31:57 2019 +0100 @@ -1,4 +1,3 @@ -Title: Author: Guru Date: 2017-12-06 14:03:55
--- a/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/5.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/5.md Thu Dec 19 09:31:57 2019 +0100 @@ -1,4 +1,3 @@ -Title: Author: Sebastian Urbanneck Date: 2019-02-14 17:43:20
--- a/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/6.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/6.md Thu Dec 19 09:31:57 2019 +0100 @@ -1,7 +1,6 @@ -Title: Author: Dirk Olmes Date: 2019-02-14 17:51:00 -ReplyTo: 5md +ReplyTo: 5.md It was a case of good old printf-style debugging back and forth that finally got me this far.
--- a/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/7.md Wed Jul 24 08:29:42 2019 +0200 +++ b/content/comments/compiling-the-shrew-soft-vpn-client-on-raspberry-pi/7.md Thu Dec 19 09:31:57 2019 +0100 @@ -1,4 +1,3 @@ -Title: Author: SalC Date: 2019-07-22 20:19:02
--- a/pelicanconf.py Wed Jul 24 08:29:42 2019 +0200 +++ b/pelicanconf.py Thu Dec 19 09:31:57 2019 +0100 @@ -4,7 +4,9 @@ AUTHOR = u'Dirk Olmes' SITENAME = u'Infoschnipsel und Wissenswertes' -SITEURL = 'http://xanthippe.duckdns.org/blog' +SITEURL = 'https://xanthippe.duckdns.org/blog' +# Uncomment following line if you want document-relative URLs when developing +RELATIVE_URLS = True ARCHIVES_URL = 'archives.html' DEFAULT_LANG = u'de' @@ -43,6 +45,3 @@ ) DEFAULT_PAGINATION = 10 - -# Uncomment following line if you want document-relative URLs when developing -RELATIVE_URLS = True