search for: prettyprint

I'd like to ask for help with a problem in CentOS 5.2 when printing from the command line with the prettyprint option selected. Program students print out their code with the command: lpr -P<printer_name> -o prettyprint -o job-sheets=none <filename_to_be_printed> The prettyprint option, as you know, puts a banner with file name and date at the top, and uses a small font, and (for a color p...

Is there a pretty-printer for R data (and code for that matter), similar to Lisp's prettyprint/grind? I've looked in CRAN, and couldn't find anything. For example, I'd like to have: prettyprint(list(a=1:20*2, b=list(data.frame(q = c(2,1,3), r = c(3,1,2), s = c(1,3,2)), as.POSIXct("2014-02-03"))) * =>* list(a = c(2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22,...

Bugs item #14298, was opened at 2007-09-28 10:23 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=14298&group_id=85 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Lars Olsson (lasso) Assigned to: Nobody (None) Summary: windows-api 0.2.0/windows-pr 0.7.1 causes segfault with require of win32/file Initial Comment:

Hi I'm using llvm-5. Browsing the source of llvm-dwarfdump and trying it on some shared libraries, I see I can print the debug info (assuming it exists). For some function, I'm wondering if there's a short cut to prettyprinting the signature of a function in the library? I think, looking at the output, that enough information exists but it seems to involve looking at the subprogram and then chasing references to parameters elsewhere in the debug info and so on. Browsing the llvm headers, I see classes like DISubprogra...

...:22 PM, Bill O'Hara via llvm-dev wrote: > Hi > > I'm using llvm-5. Browsing the source of llvm-dwarfdump and trying it on > some shared libraries, I see I can print the debug info (assuming it > exists). For some function, I'm wondering if there's a short cut to > prettyprinting the signature of a function in the library? I think, > looking at the output, that enough information exists but it seems to > involve looking at the subprogram and then chasing references to > parameters elsewhere in the debug info and so on. > > Browsing the llvm headers, I see...

I've added a few LLVM GDB pretty printers a while back (& just added llvm::Optional earlier today) & thought people might be interested in how to use them, etc. I use them by adding the following to my .gdbinit: source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py Also, I can suggest adding: set print pretty on there too, it helps a lot when printing complex nested data structures. Once you have that, you can get pretty output like this: (gdb) p Abbrev->AbbrDeclSets $1 = std::map with 1 elements = { [0] = { Offset = 0, FirstAbbrCode...

Hi I'm using llvm-5. Browsing the source of llvm-dwarfdump and trying it on some shared libraries, I see I can print the debug info (assuming it exists). For some function, I'm wondering if there's a short cut to prettyprinting the signature of a function in the library? I think, looking at the output, that enough information exists but it seems to involve looking at the subprogram and then chasing references to parameters elsewhere in the debug info and so on. Browsing the llvm headers, I see classes like DISubprogra...

...I've added a few LLVM GDB pretty printers a while back (& just added > llvm::Optional earlier today) & thought people might be interested in how > to use them, etc. > > I use them by adding the following to my .gdbinit: > > source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I can suggest adding: > > set print pretty on > > there too, it helps a lot when printing complex nested data structures. > > Once you have that, you can get pretty output like this: > > (gdb) p Abbrev->AbbrDeclSets > $1 = std::map with 1 elemen...

...VM GDB pretty printers a while back (& just added >> llvm::Optional earlier today) & thought people might be interested in how >> to use them, etc. >> >> I use them by adding the following to my .gdbinit: >> >> source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py >> >> Also, I can suggest adding: >> >> set print pretty on >> >> there too, it helps a lot when printing complex nested data structures. >> >> Once you have that, you can get pretty output like this: >> >> (gdb) p Abbrev->AbbrD...

...I've added a few LLVM GDB pretty printers a while back (& just added > llvm::Optional earlier today) & thought people might be interested in how > to use them, etc. > > I use them by adding the following to my .gdbinit: > > source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I can suggest adding: > > set print pretty on > > there too, it helps a lot when printing complex nested data structures. > > Once you have that, you can get pretty output like this: > > (gdb) p Abbrev->AbbrDeclSets > $1 = std::map with 1 elemen...

...VM GDB pretty printers a while back (& just added >> llvm::Optional earlier today) & thought people might be interested in how >> to use them, etc. >> >> I use them by adding the following to my .gdbinit: >> >> source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py >> >> Also, I can suggest adding: >> >> set print pretty on >> >> there too, it helps a lot when printing complex nested data structures. >> >> Once you have that, you can get pretty output like this: >> >> (gdb) p Abbrev->AbbrD...

...I've added a few LLVM GDB pretty printers a while back (& just added > llvm::Optional earlier today) & thought people might be interested in how > to use them, etc. > > I use them by adding the following to my .gdbinit: > > source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I can suggest adding: > > set print pretty on > > there too, it helps a lot when printing complex nested data structures. > > Once you have that, you can get pretty output like this: > > (gdb) p Abbrev->AbbrDeclSets > $1 = std::map with 1 elemen...

...VM GDB pretty printers a while back (& just added >> llvm::Optional earlier today) & thought people might be interested in how >> to use them, etc. >> >> I use them by adding the following to my .gdbinit: >> >> source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py >> >> Also, I can suggest adding: >> >> set print pretty on >> >> there too, it helps a lot when printing complex nested data structures. >> >> Once you have that, you can get pretty output like this: >> >> (gdb) p Abbrev->AbbrD...

...I've added a few LLVM GDB pretty printers a while back (& just added > llvm::Optional earlier today) & thought people might be interested in how > to use them, etc. > > I use them by adding the following to my .gdbinit: > > source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I can suggest adding: > > set print pretty on > > there too, it helps a lot when printing complex nested data structures. > > Once you have that, you can get pretty output like this: > > (gdb) p Abbrev->AbbrDeclSets > $1 = std::map with 1 elemen...

...the pretty printers for more types the elements should be self explanatory. Patches and feedback welcome to add more visualizers, improve existing ones, etc. *How do you access/use these pretty printers?* Currently, the simplest thing to do is: source /path/to/your/llvm/src/utils/gdb-scripts/prettyprinters.py You can put this in your ~/.gdbinit if you want to make it more convenient. *Possible Usability Improvements* Just sourcing in .gdbinit doesn't scale if you have multiple LLVM source trees or debug builds that might be out of sync with one another (the ABI of the ADTs probably doesn...

...necessary, setup a new printer going directly to that IP address, but I'd like some control over the que. I just sent a job to the .38, and here's the first part of the error_log: StartJob: argv = "paper1","63","root","test1.txt","1","prettyprint","/var/spool/cups/d00063-0 01" D [18/Nov/2002:10:54:22 -0600] StartJob: envp = "PATH=/usr/lib/cups/filter:/bin:/usr/bin","SOFTWARE=CUPS/1.1","USER=root","C HARSET=iso-8859-1","LANG=en_US","TZ=GMT","PPD=/etc/cups/ppd/pap...

Paul wrote to R-devel : PaulG> ts() is giving me problems on Solaris: PaulG> R : Copyright 1999, The R Development Core Team PaulG> Version 0.64.0 (April 8, 1999) PaulG> ... >> z <- ts(matrix(1:20,10,2), start=c(1969,1), frequency=12) >> max(abs(z-z)) PaulG> Error: invalid time series parameters specified >> traceback()

...t markdown-formatted plain text to HTML, LaTeX, ConTeXt, DocBook XML, groff man pages, S5 HTML slide shows, RTF, reStructuredText, and (using the associated shell script markdown2pdf) PDF. You can also convert HTML, LaTeX, and reStructuredText to markdown. You can even convert markdown to markdown (prettyprinting). Pandoc supports a number of extensions to standard markdown syntax (all of which can be disabled by using the --strict option): - Document metadata (title, author, date) - Footnotes - Tables - Definition lists - Superscripts and subscripts - Strikeout - Inline LaTeX math and La...

...;string>", line 1, in <lambda> File "/usr/lib64/python2.7/site-packages/xen/xm/main.py", line 1589, in xm_importcommand cmd.main([command] + args) File "/usr/lib64/python2.7/site-packages/xen/xm/create.py", line 1553, in main from xml.dom.ext import PrettyPrint as XMLPrettyPrint ImportError: No module named ext On the Host I installed xen-4.0.2_02-4.7.1.x86_64 xen-libs-4.0.2_02-4.7.1.x86_64 xen-tools-4.0.2_02-4.7.1.x86_64 The config file I''m using is bootloader = ''/usr/lib/xen/boot/domUloader.py'' bootargs = ''--entry...

...te: > I've added a few LLVM GDB pretty printers a while back (& just added llvm::Optional earlier today) & thought people might be interested in how to use them, etc. > > I use them by adding the following to my .gdbinit: > > source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I can suggest adding: > > set print pretty on > > there too, it helps a lot when printing complex nested data structures. > > Once you have that, you can get pretty output like this: > > (gdb) p Abbrev->AbbrDeclSets > $1 = std::map with 1 e...