Hide/Show, Fold Code Blocks & Selective Display
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Doxydoxygen User Guide Release 0.79.4
DoxyDoxygen User Guide Release 0.79.4 20Tauri Aug 16, 2021 MANUAL 1 Welcome to DoxyDoxygen 1 2 Installation 3 2.1 Software installation with Package Control...............................3 2.2 Manual software installation.......................................3 2.3 License installation............................................4 2.4 EULA (End User License Agreement)..................................4 2.4.1 Licenses.............................................4 2.4.2 Description of other rights and limitations...........................4 2.4.3 No warranties..........................................5 3 Usage 7 3.1 Create a documentation block......................................7 3.2 Update / wrap an existing documentation block.............................8 3.3 Switch between comment styles.....................................9 3.4 Extend a documentation block......................................9 3.4.1 Auto-completion........................................9 3.4.2 Comment continuation..................................... 10 3.5 Navigate in documentation........................................ 10 3.5.1 Move to the right column.................................... 10 3.5.2 Follow references........................................ 10 3.6 Fold / Unfold comments......................................... 11 3.7 Translate................................................. 11 3.8 Generate documentation......................................... 12 4 Customization 13 4.1 Settings.................................................. 13 4.1.1 Understand -
Tuto Documentation Release 0.1.0
Tuto Documentation Release 0.1.0 DevOps people 2020-05-09 09H16 CONTENTS 1 Documentation news 3 1.1 Documentation news 2020........................................3 1.1.1 New features of sphinx.ext.autodoc (typing) in sphinx 2.4.0 (2020-02-09)..........3 1.1.2 Hypermodern Python Chapter 5: Documentation (2020-01-29) by https://twitter.com/cjolowicz/..................................3 1.2 Documentation news 2018........................................4 1.2.1 Pratical sphinx (2018-05-12, pycon2018)...........................4 1.2.2 Markdown Descriptions on PyPI (2018-03-16)........................4 1.2.3 Bringing interactive examples to MDN.............................5 1.3 Documentation news 2017........................................5 1.3.1 Autodoc-style extraction into Sphinx for your JS project...................5 1.4 Documentation news 2016........................................5 1.4.1 La documentation linux utilise sphinx.............................5 2 Documentation Advices 7 2.1 You are what you document (Monday, May 5, 2014)..........................8 2.2 Rédaction technique...........................................8 2.2.1 Libérez vos informations de leurs silos.............................8 2.2.2 Intégrer la documentation aux processus de développement..................8 2.3 13 Things People Hate about Your Open Source Docs.........................9 2.4 Beautiful docs.............................................. 10 2.5 Designing Great API Docs (11 Jan 2012)................................ 10 2.6 Docness................................................. -
Reproducible Research for Empirical Economics & Econometrics
How To Make A Pie: Reproducible Research for Empirical Economics & Econometrics Valérie Orozco, Christophe Bontemps, Elise Maigne, Virginie Piguet, Annie Hofstetter, Anne Marie Lacroix, Fabrice Levert, Jean-Marc Rousselle To cite this version: Valérie Orozco, Christophe Bontemps, Elise Maigne, Virginie Piguet, Annie Hofstetter, et al.. How To Make A Pie: Reproducible Research for Empirical Economics & Econometrics. 2019. hal-02025843 HAL Id: hal-02025843 https://hal.archives-ouvertes.fr/hal-02025843 Preprint submitted on 19 Feb 2019 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. TSE ‐ 933 July 2018 “How To Make A Pie: Reproducible Research for Empirical Economics & Econometrics" V. Orozco, C. Bontemps, E. Maigné, V. Piguet, A. Hofstetter, A. Lacroix, F. Levert, J.M. Rousselle How To Make A Pie: Reproducible Research for Empirical Economics & Econometrics∗ V. Orozco,y C. Bontemps,y E. Maigné,z V. Piguet,§ A. Hofstetter,{ A. Lacroix,k F. Levert,∗∗ J.M. Rousselle{ June 2018yy Abstract Empirical economics and econometrics (EEE) research now relies primarily on the applica- tion of code to datasets. Handling the workflow linking datasets, programs, results and finally manuscript(s) is essential if one wish to reproduce results, which is now increasingly required by journals and institutions. -
Evolution of Emacs Lisp
Evolution of Emacs Lisp STEFAN MONNIER, Université de Montréal, Canada MICHAEL SPERBER, Active Group GmbH, Germany 74 Shepherd: Brent Hailpern, IBM Research, USA While Emacs proponents largely agree that it is the world’s greatest text editor, it is almost as much a Lisp machine disguised as an editor. Indeed, one of its chief appeals is that it is programmable via its own programming language. Emacs Lisp is a Lisp in the classic tradition. In this article, we present the history of this language over its more than 30 years of evolution. Its core has remained remarkably stable since its inception in 1985, in large part to preserve compatibility with the many third-party packages providing a multitude of extensions. Still, Emacs Lisp has evolved and continues to do so. Important aspects of Emacs Lisp have been shaped by concrete requirements of the editor it supports as well as implementation constraints. These requirements led to the choice of a Lisp dialect as Emacs’s language in the first place, specifically its simplicity and dynamic nature: Loading additional Emacs packages orchanging the ones in place occurs frequently, and having to restart the editor in order to re-compile or re-link the code would be unacceptable. Fulfilling this requirement in a more static language would have been difficult atbest. One of Lisp’s chief characteristics is its malleability through its uniform syntax and the use of macros. This has allowed the language to evolve much more rapidly and substantively than the evolution of its core would suggest, by letting Emacs packages provide new surface syntax alongside new functions. -
Scribble: Closing the Book on Ad Hoc Documentation Tools
Scribble: Closing the Book on Ad Hoc Documentation Tools Matthew Flatt Eli Barzilay Robert Bruce Findler University of Utah and PLT Northeastern University and PLT Northwestern University and PLT mfl[email protected] [email protected] [email protected] Abstract Scribble is a system for writing library documentation, user guides, and tutorials. It builds on PLT Scheme’s technology for language extension, and at its heart is a new approach to connecting prose references with library bindings. Besides the base system, we have built Scribble libraries for JavaDoc-style API documentation, liter- ate programming, and conference papers. We have used Scribble to produce thousands of pages of documentation for PLT Scheme; the new documentation is more complete, more accessible, and bet- ter organized, thanks in large part to Scribble’s flexibility and the ease with which we cross-reference information across levels. This paper reports on the use of Scribble and on its design as both an extension and an extensible part of PLT Scheme. Categories and Subject Descriptors I.7.2 [Document and Text Processing]: Document Preparation—Languages and systems General Terms Design, Documentation, Languages 1. Documentation as Code Most existing documentation tools fall into one of three categories: LATEX-like tools that know nothing about source code; JavaDoc- like tools that extract documentation from annotations in source code; and WEB-like literate-programming tools where source code is organized around a prose presentation. Scribble is a new documentation infrastructure for PLT Scheme Figure 1: DrScheme with binding arrows and documentation links that can support and integrate all three kinds of tools. -
CFFI User Manual
CFFI User Manual Copyright c 2005 James Bielman <jamesjb at jamesjb.com> Copyright c 2005-2015 Lu´ısOliveira <loliveira at common-lisp.net> Copyright c 2005-2006 Dan Knapp <danka at accela.net> Copyright c 2005-2006 Emily Backes <lucca at accela.net> Copyright c 2006 Stephen Compall <s11 at member.fsf.org> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. The software is provided \as is", without warranty of any kind, ex- press or implied, including but not limited to the warranties of mer- chantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software. i Table of Contents 1 Introduction ::::::::::::::::::::::::::::::::::::: 1 2 Installation::::::::::::::::::::::::::::::::::::::: 2 3 Implementation Support :::::::::::::::::::::::: 3 3.1 Limitations ::::::::::::::::::::::::::::::::::::::::::::::::::::: -
Scribble: Closing the Book on Ad Hoc Documentation Tools
Scribble: Closing the Book on Ad Hoc Documentation Tools Matthew Flatt Eli Barzilay Robert Bruce Findler University of Utah and PLT Northeastern University and PLT Northwestern University and PLT mfl[email protected] [email protected] [email protected] Abstract Scribble is a system for writing library documentation, user guides, and tutorials. It builds on PLT Scheme’s technology for language extension, and at its heart is a new approach to connecting prose references with library bindings. Besides the base system, we have built Scribble libraries for JavaDoc-style API documentation, liter- ate programming, and conference papers. We have used Scribble to produce thousands of pages of documentation for PLT Scheme; the new documentation is more complete, more accessible, and bet- ter organized, thanks in large part to Scribble’s flexibility and the ease with which we cross-reference information across levels. This paper reports on the use of Scribble and on its design as both an extension and an extensible part of PLT Scheme. Categories and Subject Descriptors I.7.2 [Document and Text Processing]: Document Preparation—Languages and systems General Terms Design, Documentation, Languages 1. Documentation as Code Most existing documentation tools fall into one of three categories: LATEX-like tools that know nothing about source code; JavaDoc- like tools that extract documentation from annotations in source code; and WEB-like literate-programming tools where source code is organized around a prose presentation. Scribble is a new documentation infrastructure for PLT Scheme Figure 1: DrScheme with binding arrows and documentation links that can support and integrate all three kinds of tools.