Displaying 20 results from an estimated 45 matches for "pygmentize".
2011 Feb 07
8
Pygments
The Pygments highlighter supports many more languages than CodeRay.
Pygments is written in Python, but I''ve seen non-Python projects use it
(Jekyll, Pygments).
There''s also this: https://github.com/nex3/rb-pygments
Any idea how much work it would be to add Pygments support to Webgen?
2008 Mar 27
1
R Code and the Pygments Python SyntaxHighlighter
Dear R Help,
is someone going to write a R/S language lexer for the Pygments Python syntax
highlighter <http://pygments.org/>? As it is used now by Trac, Django, or the
Python documentation tool Sphinx, the R community can apply it in Python-based
Wikis like Moinmoin and others.
Hans Werner
2020 Jan 23
2
[cfe-dev] Phabricator -> GitHub PRs?
> On Jan 23, 2020, at 08:37, David Greene via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hubert Tong <hubert.reinterpretcast at gmail.com> writes:
>
>>> I read this as the refresh being an entirely new GitHub PR. Is that
>>> right? Normally I would expect the same PR to be used but the rebase
>>> would cause a force-push of the branch
2013 Nov 25
0
[LLVMdev] Language Reference bug?
On Sun, Nov 24, 2013 at 10:19 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> Hi,
>
> The language reference uses "::" many places where it seems it should be
> using ".. code-block:: llvm". The result is that Sphinx does not colorize
> these samples.
>
> Should I fix this? Or is it purposeful?
>
Could you give an example of what you are
2013 Nov 25
2
[LLVMdev] Language Reference bug?
Hi,
The language reference uses "::" many places where it seems it should be
using ".. code-block:: llvm". The result is that Sphinx does not colorize
these samples.
Should I fix this? Or is it purposeful?
Also, anybody but me that has noticed that Sphinx does not always colorize
things even if you put the proper ".. code-block:: llvm" in front? If it
is a known
2013 Jan 22
0
[LLVMdev] LLVM TblGen syntax hightlighter
Hi all,
LLVM now is using Sphinx to generate it's documentation. For syntax
hightlighting, Sphinx uses Pygments [2]. Pygments already support LLVM
IR syntax, however it doesn't support LLVM tblgen. I wrote up a Pygments
extension that can be incorpreated in Sphinx [3]. After installing the
extension, you can write the code below and get hightlight tblgen
syntax.
.. code-block:: tblgen
2012 Nov 27
4
[LLVMdev] [RFC] Removal of 'deplibs'?
Hi all,
Did you know that there is a 'deplibs' keyword? Neither did I. It looks like it's not really used for much. We don't document it in the Language Reference. The only support I see if for reading/writing bitcode and manipulating modules. There's a bunch of code that could be removed if we could get rid of this.
Does anyone use this thing? Does anyone mind if I nuke it?
2020 Jan 22
3
[cfe-dev] Phabricator -> GitHub PRs?
On Wed, Jan 22, 2020 at 4:40 PM David Greene <greened at obbligato.org> wrote:
> Hubert Tong <hubert.reinterpretcast at gmail.com> writes:
>
> > The update process in Phab in rather manual and it does lead to more
> noise.
> > The GitHub force push risks loss of context for earlier comments (not
> just
> > in terms of display, like viewing older comments
2018 Feb 13
1
Syntax highlighting
Hi,
I would like know if there are any plans for some "standardized" syntax
highlighting of R code?
* Currently I'm using minted for my LaTeX slides with pygmentize and I
do not know what scheme is used for highlighting the R code.
* RStudio uses (as default) TextMate (Text editor for MacOS)
highlighting for R code.
* The R package "highr" just defines CSS classes and does not provide
any default CSS file, but embeds andre simons Highlight 3.42 So...
2009 Feb 25
5
[Cucumber] pretty html output?
Cucumberists (and RSpec Classic users ;):
How can we convert a Cucumber feature file into HTML with syntax highlighting?
Not the test-runner output; that''s preprocessed so it does not match the input
file...
Tx!
--
Phlip
2019 May 08
2
failed to build llvm since 25de7691a0e27c29c8d783a22373cc265571f5e9 on AMD platform
Hi
we observed that below errors occur on AMD platform since 25de7691a0e27c29c8d783a22373cc265571f5e9
root at lkp-opteron1 /opt/rootfs/llvm_project/src/build# cmake -DCMAKE_BUILD_TYPE=release -DLLVM_ENABLE_PROJECTS=clang -G "Unix Makefiles" ../llvm -DCMAKE_INSTALL_PREFIX=/opt/cross/
-- clang project is enabled
-- clang-tools-extra project is disabled
-- compiler-rt project is disabled
2019 May 09
3
failed to build llvm since 25de7691a0e27c29c8d783a22373cc265571f5e9 on AMD platform
LKP framework can guarantee that all the software environment are same on AMD and INTEL platform.
INTEL platform always work well, after revert this patch, AMD works well.
we tried below commit on AMD.
1) 25de7691a0e27c29c8d783a22373cc265571f5e9: bad
2) a82235843b102202766115e10003c9465a8b83ae: good
the error logs(build/CMakeFiles/CMakeError.log) has no difference b/w 1) and 2) on AMD platform
2019 Dec 20
4
Upgrading from Debian Stretch to Buster, Van Belle package
Ah, ok,
apt-get remove libldb1 ldb-tools
Then try again : apt install samba winbind acl
The replacement of libldb1 to libldb2 is missing something.
I'll have a look at that.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: Lmloge [mailto:lmloge at orange.fr]
> Verzonden: vrijdag 20 december 2019 13:15
> Aan: L.P.H. van Belle
> CC: samba at lists.samba.org
2010 Aug 09
1
[LLVMdev] [RFC] Moving to Sphinx for LLVM and friends documentation (with partial implementation (in both 10pt and 12pt font)).
Michael,
The benefits of Sphinx sound nice but one comment: The main page and the tables of contents in the other pages (at least the ones I looked at: Getting Started; Lang Ref) are so long and sparse that it is difficult to get the big picture of what is there and even to find a document unless you know what to search for. The originals were much more compact and so much better in this regard.
2019 Dec 20
0
Upgrading from Debian Stretch to Buster, Van Belle package
Hello Louis,
-----------------------------------
# apt-get remove libldb1 ldb-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
? libtalloc2 libtdb1 libtevent0
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
? ldb-tools libldb1
0
2016 Nov 12
5
Rewriting opt-viewer in C++
Hi Adam,
Thank you for writing opt-viewer! I've been playing around with it and found it helps me understand what optimizations were performed, which were missed, and why, as well as easily navigate to the relevant code. Wanting to use it on larger projects, I found that it can take a while to analyze the optimization reports. Since there doesn't seem to be too much code in it yet, I
2010 Dec 02
2
Any way to get syntax-highlighted code blocks with Text::MultiMarkdown?
Hello,
I'm using Text::MultiMarkdown in my website, and I would like to know if
there is any way to get syntax highlighting in code blocks.
Thanks,
-Mike Doherty
2010 Aug 09
0
[LLVMdev] [RFC] Moving to Sphinx for LLVM and friends documentation (with partial implementation (in both 10pt and 12pt font)).
Hi Michael,
Awesome work!
I'm a strong supporter of using Sphinx. I've been using it for the LNT
docs (http://llvm.org/docs/lnt/) and it is quite nice to work with. +1
for migrating over.
- Daniel
On Sun, Aug 8, 2010 at 11:29 PM, Michael Spencer <bigcheesegs at gmail.com> wrote:
> Moving the LLVM Documentation to Sphinx
> =======================================
>
>
2010 Aug 09
5
[LLVMdev] [RFC] Moving to Sphinx for LLVM and friends documentation (with partial implementation (in both 10pt and 12pt font)).
Moving the LLVM Documentation to Sphinx
=======================================
As a few of you that are on IRC already know, I have experimented with moving
the LLVM documentation over to `Sphinx <http://sphinx.pocoo.org/index.html>`__
from the current html form. I have moved almost all of the content over and have
begun "Sphinxifying" the documentation to correct links and make
2012 Jun 16
2
[LLVMdev] RFC: "Building with MinGW on Windows" (DOC, NEW)
Here's the first part of my Windows set up documentation. This one only
covers the process of setting up a normal box for building LLVM and Clang.
A later document, which will follow in a few days, will cover how to set
up a buildbot slave.
As usual: I'm not a psychic, so if you have opinions regarding or
suggestions on this document, please feel free to share them with me (on
this