GeSHi Sourceforge group redirects MediaWiki-related issues to MediaWiki. MediaWiki redirects requests & features back to SourceForge.
I modified my install to parse PHP blocks allowing to highlight HTML/JS/CSS as well.
As you know, the MediaWiki extension lives in a directory named SyntaxHighlight_GeSHi, and contains a subdirectory geshi. If your patch is to the files inside geshi, submit the patch to the GeSHi Sourceforge group. If your patch is to the files not in geshi, submit it to MediaWiki's bugzilla.
If your patch is to both, hopefully the part of the patch to files inside geshi is independently useful. If so, submit that part to the Sourceforge group and the other part to MediaWiki. If the patch to the geshi files is not independently useful, you may have problems convincing either group to take it.
I don't know this extension but you can try:
MediaWiki's BugZilla
The mailing lists, probably mediawiki-l
The MediaWiki IRC channel on Freenode
Related
I'm trying to set up a blog via Jekyll and GitHub Pages. To deploy it was not such a big deal, however, in trying to follow the steps described here I only managed to make it display the dark skin locally. Is there a way to deploy it on GithubPages as well?
I installed it via
gem "minima", git: "https://github.com/jekyll/minima"
then added the following two lines in _config.yml
minima:
skin: dark
This is the repo holding the ruby code.
i had this problem too. I learned that the software used by github pages isn’t updated often, hopefully for stability reasoning. You can check what versions they use at https://pages.github.com/versions/. The newer version of minima has the alternative “skins” sass/css feature, but the one currently on github pages doesn’t—-heck, github pages still hasn’t updated Jekyll to v4!!... You should be able to see the build error by clicking Actions on the github repo, then clicking on the last “workflow”, then click on the red-colored build. It’ll say the key in the config file doesn’t exist or somethin’ like that, on the skin: dark line.
anyway, in the config file, add remote_theme: jekyll/minima to force download the latest version from the github repo upon rebuild. Don’t use ~jekyll-theme: minima (or whatever it’s called). In fact, at the moment, all of the themes that come pre-installed with github pages are quite old now...
but really though, use the jekyll discussion site https://talk.jekyllrb.com/.
I was using Chrome, and apparently the Clear browsing data in the last hour with Cookies and other site data and Cached images and files checked made the local updates appear live.
You can go even further and make your jekyll/minima powered site respect users theme preference
https://alexander-taran.github.io/2022/06/08/adopting-dark-theme-in-jekyll-blog.html
I am working on an app that creates automatic blog HTML pages using JSON and also has to provide versioning for that blog.
Creating HTML using JSON files
Creating a GIT tag whenever User creates a version.
If the user wanted to see the previous version of that blog I am simply checking out that file to given tag and fetch the file and again creating HTML using that JSON file.
Questions
Is it right to use GIT for the above purpose?
If yes, Are there any precautions that I have to take?
If no, Is there any alternatives for saving the previous version of a file except saving each file for each version?
Note: I am using Node.js for creating GIT tags and checkout to tags
You should use git for every project, ask if it's right only if you have a ton of binary files.
I've seen people use git for content writing and articles, remember it is an efficient version control systems and as long as you wish to have past versions of your project( you always should), you should use git.
even if you are not pushing to a remote repository, it's better to have some VCS implemented in all your projects.
I'm considering setting up my own readthedocs instance. I see that they have support for Git, Mercurial, Subversion, and CVS .I do however have a couple of legacy projects which are considerable effort to move over to git sitting in TFS using TFVS.
Would it still be possible to pull in these projects using the webhook method they're talking about?
What would be the code based approach to get this to work?
Eventually I'd like to get all these opened up on Github, but thats something I still need to sell.
No, it's not support to uding tfvc with readthedocs.
It's viable to use web hooks in VSTS directly. Document from MSDN:Web Hooks
However, if you want to use web hooks with TFS. You may need to use TFS plugin such as Cloudpipes. More details you can refer this link: Integrate Team Foundation Server with Web hooks
I want to download http://code.google.com/p/android-traditional-chinese-ime/source/checkout this.
But how to use tortoiseHg2.7 with Mercurial to download the google open source code?
It looks like that project is using a Subversion repository, so if you want to get the source as a Mercurial repo, you have a couple of choices, both of which use Mercurial extensions.
One is HgSubversion, which will allow you to work directly with the Subversion repository, in theory allowing you to push changes back to the project. It doesn't come with Mercurial (or TortoiseHg) so you'd have to download it separately. I've not used it so can't really comment on it.
The other option is Convert which does come with Mercurial - you just need to enable it, which in TortoiseHg you can do by selecting user-config and checking the "Convert" box in the Extensions section. Again, I've not used it to work with a Subversion repo, so can't do much more than point you at the extension page, which has some useful information.
Alternatively you could use Subversion itself, which is more likely to work with the repository without issue. I'd recommend getting TortoiseSVN - it should do just what you want.
I found this site that has a link to a .Net project.
The link is to a folder structure.
How do I down load this project without SVN??
Is it specific SVN??
http://svn2.assembla.com/svn/nbdn_web_store/
Source Code
I would say that either you install svn (which is not a huge install), or you have a lot of clicking to do when you download each file separately using your web browser. Can't see any other alternatives, really.
install subversion and check out the file with e.g. the command
svn co http://svn2.assembla.com/svn/nbdn_web_store/trunk/ ndbn_web_store
First of all, I agree that installing svn is a good option.
If you don't want to do that (and don't like clicking tons of links to download each file) you can use an offline browser such as this one recommended by CNET