DOCSLIB.ORG

Leo API Documentation Release 4.11Dev

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Leo API Documentation Release 4.11Dev Leo API Documentation Release 4.11dev Ed K. Ream May 31, 2018 Contents 1 leo Package 3 1.1 leo Package...............................................3 1.2 Subpackages...............................................3 1.2.1 core Package..........................................3 1.2.1.1 core Package.....................................3 1.2.1.2 bzr_version Module...............................3 1.2.1.3 format-code Module...............................3 1.2.1.4 leoApp Module...................................3 1.2.1.5 leoAtFile Module................................. 11 1.2.1.6 leoBridge Module................................. 22 1.2.1.7 leoBridgeTest Module.............................. 23 1.2.1.8 leoCache Module.................................. 23 1.2.1.9 leoChapters Module............................... 25 1.2.1.10 leoColor Module.................................. 27 1.2.1.11 leoCommands Module............................... 28 1.2.1.12 leoCompare Module................................ 40 1.2.1.13 leoConfig Module................................. 42 1.2.1.14 leoDebugger Module............................... 42 1.2.1.15 leoDynamicTest Module............................. 42 1.2.1.16 leoEditCommands Module............................ 43 1.2.1.17 leoFileCommands Module............................ 43 1.2.1.18 leoFind Module................................... 48 1.2.1.19 leoFrame Module.................................. 57 1.2.1.20 leoGlobals Module................................ 57 1.2.1.21 leoGui Module................................... 83 1.2.1.22 leoIPython Module................................ 83 1.2.1.23 leoImport Module................................. 83 1.2.1.24 leoInspect Module................................ 89 1.2.1.25 leoKeys Module................................... 89 1.2.1.26 leoMenu Module................................... 101 1.2.1.27 leoNodes Module.................................. 103 1.2.1.28 leoPlugins Module................................ 117 1.2.1.29 leoPymacs Module................................. 120 1.2.1.30 leoRst Module................................... 120 1.2.1.31 leoSessions Module............................... 120 1.2.1.32 leoShadow Module................................. 121 i 1.2.1.33 leoTangle Module................................. 124 1.2.1.34 leoTest Module................................... 128 1.2.1.35 leoUndo Module................................... 128 1.2.1.36 leoVersion Module................................ 132 1.2.1.37 runLeo Module................................... 132 1.2.2 extensions Package....................................... 132 1.2.2.1 extensions Package................................ 132 1.2.2.2 asciidoc Module.................................. 132 1.2.2.3 colors Module................................... 149 1.2.2.4 patch_11_01 Module............................... 149 1.2.2.5 sh Module....................................... 150 1.2.2.6 testExtension Module.............................. 150 1.2.3 external Package........................................ 150 1.2.3.1 external Package.................................. 150 1.2.3.2 codewise Module.................................. 150 1.2.3.3 edb Module...................................... 154 1.2.3.4 ipy_leo Module................................... 163 1.2.3.5 leoSAGlobals Module............................... 163 1.2.3.6 leoftsindex Module............................... 170 1.2.3.7 leosax Module................................... 170 1.2.3.8 lproto Module................................... 171 1.2.3.9 stringlist Module................................ 171 1.2.3.10 Subpackages...................................... 172 1.2.4 plugins Package......................................... 177 1.2.4.1 plugins Package.................................. 177 1.2.4.2 FileActions Module............................... 177 1.2.4.3 active_path Module............................... 178 1.2.4.4 add_directives Module............................. 181 1.2.4.5 at_folder Module................................. 181 1.2.4.6 at_produce Module................................ 182 1.2.4.7 at_view Module................................... 182 1.2.4.8 attrib_edit Module............................... 182 1.2.4.9 backlink Module.................................. 182 1.2.4.10 baseNativeTree Module............................. 182 1.2.4.11 bibtex Module................................... 182 1.2.4.12 bigdash Module................................... 184 1.2.4.13 bookmarks Module................................. 184 1.2.4.14 bzr_qcommands Module.............................. 184 1.2.4.15 chapter_hoist Module.............................. 184 1.2.4.16 codewisecompleter Module........................... 184 1.2.4.17 colorize_headlines Module.......................... 184 1.2.4.18 contextmenu Module............................... 184 1.2.4.19 ctagscompleter Module............................. 184 1.2.4.20 cursesGui Module................................. 184 1.2.4.21 datenodes Module................................. 184 1.2.4.22 debugger_pudb Module.............................. 185 1.2.4.23 dragdropgoodies Module............................ 185 1.2.4.24 dtest Module.................................... 185 1.2.4.25 dump_globals Module............................... 186 1.2.4.26 empty_leo_file Module............................. 186 1.2.4.27 enable_gc Module................................. 186 1.2.4.28 expfolder Module................................. 187 1.2.4.29 free_layout Module............................... 187 1.2.4.30 ftp Module...................................... 187 ii 1.2.4.31 geotag Module................................... 187 1.2.4.32 gitarchive Module................................ 187 1.2.4.33 graphcanvas Module............................... 188 1.2.4.34 gtkDialogs Module................................ 188 1.2.4.35 gtkGui Module................................... 188 1.2.4.36 import_cisco_config Module......................... 188 1.2.4.37 initinclass Module............................... 188 1.2.4.38 interact Module.................................. 189 1.2.4.39 internal_ipkernel Module........................... 189 1.2.4.40 ipython Module................................... 189 1.2.4.41 ironPythonGui Module.............................. 189 1.2.4.42 jinjarender Module............................... 189 1.2.4.43 leoOPML Module................................... 189 1.2.4.44 leo_interface Module.............................. 193 1.2.4.45 leo_pdf Module................................... 194 1.2.4.46 leo_to_html Module............................... 201 1.2.4.47 leo_to_rtf Module................................ 205 1.2.4.48 leocursor Module................................. 206 1.2.4.49 leofeeds Module.................................. 207 1.2.4.50 leofts Module................................... 208 1.2.4.51 leomail Module................................... 208 1.2.4.52 leomylyn Module.................................. 208 1.2.4.53 leoremote Module................................. 208 1.2.4.54 leoscreen Module................................. 208 1.2.4.55 lineNumbers Module............................... 208 1.2.4.56 livecode Module.................................. 209 1.2.4.57 macros Module................................... 209 1.2.4.58 maximizeNewWindows Module.......................... 210 1.2.4.59 mime Module..................................... 210 1.2.4.60 mnplugins Module................................. 211 1.2.4.61 mod_autosave Module............................... 211 1.2.4.62 mod_framesize Module.............................. 211 1.2.4.63 mod_http Module.................................. 212 1.2.4.64 mod_leo2ascd Module............................... 218 1.2.4.65 mod_read_dir_outline Module........................ 219 1.2.4.66 mod_scripting Module.............................. 219 1.2.4.67 mod_speedups Module............................... 219 1.2.4.68 mod_tempfname Module.............................. 220 1.2.4.69 mod_timestamp Module.............................. 220 1.2.4.70 multifile Module................................. 220 1.2.4.71 nav_qt Module................................... 221 1.2.4.72 nested_splitter Module............................ 221 1.2.4.73 niceNosent Module................................ 221 1.2.4.74 nodeActions Module............................... 221 1.2.4.75 nodediff Module.................................. 224 1.2.4.76 nodetags Module.................................. 226 1.2.4.77 nodewatch Module................................. 226 1.2.4.78 notebook Module.................................. 226 1.2.4.79 open_shell Module................................ 226 1.2.4.80 outline_export Module............................. 227 1.2.4.81 paste_as_headlines Module.......................... 227 1.2.4.82 pluginsTest Module............................... 227 1.2.4.83 plugins_menu Module............................... 227 1.2.4.84 pretty_print Module............................... 228 iii 1.2.4.85 projectwizard Module.............................. 229 1.2.4.86 python_terminal Module............................ 229 1.2.4.87 qtGui Module.................................... 229 1.2.4.88 qt_main Module................................... 229 1.2.4.89 qt_quicksearch Module............................. 229 1.2.4.90 qtframecommands Module............................ 229 1.2.4.91 quickMove Module................................. 229 1.2.4.92 quicksearch Module............................... 229 1.2.4.93 quit_leo
Load more

Recommended publications
  • The Open Pitt What's Cooking in Linux and Open Source in Western Pennsylvania Issue 31 January 2007
    The Open Pitt What's cooking in Linux and Open Source in Western Pennsylvania Issue 31 January 2007 www.wplug.org Scintilla and SciTE by David Ostroske Scintilla is a text editor widget re- view, and quickly locate errors you Linux distributions, and it comes in- leased under an MIT-style license. If might have in your code. cluded with some versions of Ruby. this leaves you wondering “what's a As for me, I just use it to edit plain There are also plenty of other Scin- widget?,” it's basically a component text files. I could get along with using tilla-based applications available. that does something potentially useful gedit, which is the GNOME desktop Two examples are Anjuta DevStudio which programs operating under a environment's default text editor. But <http://anjuta.sourceforge.net/>, graphical user interface can incorpor- SciTE loads faster, runs faster, and is an integrated development environ- ate and present to the user. As a wid- more powerful. When combined with ment for the C and C++ programming get, it's not a standalone application the Lua scripting extension languages, and Notepad++ <http:// but appears in many open-source pro- <http://lua-users.org/wiki/ notepad-plus.sourceforge.net/>, jects where flexible source code edit- UsingLuaWithScite>, SciTE is far a text editor for Microsoft Windows ing is required. more customizable than gedit will released under the GNU General Pub- SciTE, the Scintilla Text Editor, is ever be. Plus, it can be configured to lic License. Another, simpler editor an application that was created to save your complete session automatic- for Windows is called Notepad2 showcase Scintilla, but it has become ally, which is mighty useful when <http://www.flos-freeware.ch/ a top-notch editor in its own regard.
    [Show full text]
  • The Scite – TEX Integration
    Hans Hagen VOORJAAR 2004 21 The Scite – TEX integration Abstract Editors are a sensitive, often emotional subject. Some editors have exactly the properties a software designer or a writer desires and one gets attached to it. Still, most computer experts such as TEX users often are use three or more different editors each day. Scite is a modern programmers editor which is very flexible, very configurable, and easily extended. We integrated Scite with TEX, CONTEXT, LATEX, METAPOST and viewer and succeeded in that it is now possible to design and write your texts, manuscripts, reports, manuals and books with the Scite editor without having to leave the editor to compile and view your work. The article describes what is available and what you need with special emphasis on highlighting commands with lexers. About Scite Scite is a source code editor written by Neil Hodgson. After playing with several editors we found that this editor is quite configurable and extendible. At PRAGMA ADE we use TEXEDIT, an editor written long ago in Niklaus Wirth’s MODULA as well as a platform independent reimplementation of it called TEXWORK written in PERL/TK. Although our editors possess some functionality that is not (yet) present in Scite, we decided to use Scite because it frees us from the editor maintenance chore. Installing Scite Installing Scite is straightforward. We assume below that you use MS WINDOWS but for other operating systems installation is not much different. First you need to fetch the archive from: www.scintilla.org The MS WINDOWS binaries are in wscite.zip, and you can unzip this in any direc- tory as long as the binary executable ends up in your PATH or as shortcut icon on your desktop.
    [Show full text]
  • Appendix a the Ten Commandments for Websites
    Appendix A The Ten Commandments for Websites Welcome to the appendixes! At this stage in your learning, you should have all the basic skills you require to build a high-quality website with insightful consideration given to aspects such as accessibility, search engine optimization, usability, and all the other concepts that web designers and developers think about on a daily basis. Hopefully with all the different elements covered in this book, you now have a solid understanding as to what goes into building a website (much more than code!). The main thing you should take from this book is that you don’t need to be an expert at everything but ensuring that you take the time to notice what’s out there and deciding what will best help your site are among the most important elements of the process. As you leave this book and go on to updating your website over time and perhaps learning new skills, always remember to be brave, take risks (through trial and error), and never feel that things are getting too hard. If you choose to learn skills that were only briefly mentioned in this book, like scripting, or to get involved in using content management systems and web software, go at a pace that you feel comfortable with. With that in mind, let’s go over the 10 most important messages I would personally recommend. After that, I’ll give you some useful resources like important websites for people learning to create for the Internet and handy software. Advice is something many professional designers and developers give out in spades after learning some harsh lessons from what their own bitter experiences.
    [Show full text]
  • The Pretzel User Manual
    The PretzelBook second edition Felix G¨artner June 11, 1998 2 Contents 1 Introduction 5 1.1 Do Prettyprinting the Pretzel Way . 5 1.2 History . 6 1.3 Acknowledgements . 6 1.4 Changes to second Edition . 6 2 Using Pretzel 7 2.1 Getting Started . 7 2.1.1 A first Example . 7 2.1.2 Running Pretzel . 9 2.1.3 Using Pretzel Output . 9 2.2 Carrying On . 10 2.2.1 The Two Input Files . 10 2.2.2 Formatted Tokens . 10 2.2.3 Regular Expressions . 10 2.2.4 Formatted Grammar . 11 2.2.5 Prettyprinting with Format Instructions . 12 2.2.6 Formatting Instructions . 13 2.3 Writing Prettyprinting Grammars . 16 2.3.1 Modifying an existing grammar . 17 2.3.2 Writing a new Grammar from Scratch . 17 2.3.3 Context Free versus Context Sensitive . 18 2.3.4 Available Grammars . 19 2.3.5 Debugging Prettyprinting Grammars . 19 2.3.6 Experiences . 21 3 Pretzel Hacking 23 3.1 Adding C Code to the Rules . 23 3.1.1 Example for Tokens . 23 3.1.2 Example for Grammars . 24 3.1.3 Summary . 25 3.1.4 Tips and Tricks . 26 3.2 The Pretzel Interface . 26 3.2.1 The Prettyprinting Scanner . 27 3.2.2 The Prettyprinting Parser . 28 3.2.3 Example . 29 3.3 Building a Pretzel prettyprinter by Hand . 30 3.4 Obtaining a Pretzel Prettyprinting Module . 30 3.4.1 The Prettyprinting Scanner . 30 3.4.2 The Prettyprinting Parser . 31 3.5 Multiple Pretzel Modules in the same Program .
    [Show full text]
  • Editors Desk ...2
    The content of this magazine is released under the Creative Commons Attribution-Share Alike 3.0 Unported license. For more information visit user http://creativecommons.org/licenses/by-sa/3.0 TM Issue #1 - April 2009 EDITORS DESK ................................ 2 COMMUNITY NEWS ........................ 3 CHOOSING A DE/WM ...................... 4 HARDENING SSH IN 60 SECONDS .................................... 6 GAMERS CORNER .......................... 9 TIPS & TRICKS ............................... 10 PIMP MY ARCH .............................. 11 SOFTWARE REVIEW ......................12 Q&A ..................................................14 EEDDIITTOORRSS DDEESSKK Welcome to the first issue of Arch User Magazine! ARCH USER STAFF Daniel Griffiths (Ghost1227) ........... Editor ello, and thank you for picking up issue #1 of Arch User Magazine! While David Crouse (Crouse) .......... Contributor the vast majority of you probably know me (or have at least seen me H around the forums), I feel that I should take a moment to introduce myself. My name is Daniel Griffiths, and I am a 26-year-old independent contractor in Delaware, US. Throughout my life, I have wandered through various UNIX/Linux systems including (but not limited to) MINIX, RedHat, Mandrake, Slackware, Gentoo, Debian, and even two home made distributions based on Linux From Scratch. I finally found Arch in 2007 and instantly fell in love with its elegant simplicity. Some of our more attentive readers may note that Arch already has a monthly newsletter. With the existence of the aformentioned newsletter, what is the point of adding another news medium to the mix? Fear not, newsletter readers, I have no intention of letting Arch User Magazine take the place of the newsletter. In fact, Arch User Magazine and the newsletter are intended to fill two very different needs in the Arch community.
    [Show full text]
  • ESS — Emacs Speaks Statistics
    ESS — Emacs Speaks Statistics ESS version 5.14 The ESS Developers (A.J. Rossini, R.M. Heiberger, K. Hornik, M. Maechler, R.A. Sparapani, S.J. Eglen, S.P. Luque and H. Redestig) Current Documentation by The ESS Developers Copyright c 2002–2010 The ESS Developers Copyright c 1996–2001 A.J. Rossini Original Documentation by David M. Smith Copyright c 1992–1995 David M. Smith Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Chapter 1: Introduction to ESS 1 1 Introduction to ESS The S family (S, Splus and R) and SAS statistical analysis packages provide sophisticated statistical and graphical routines for manipulating data. Emacs Speaks Statistics (ESS) is based on the merger of two pre-cursors, S-mode and SAS-mode, which provided support for the S family and SAS respectively. Later on, Stata-mode was also incorporated. ESS provides a common, generic, and useful interface, through emacs, to many statistical packages. It currently supports the S family, SAS, BUGS/JAGS, Stata and XLisp-Stat with the level of support roughly in that order. A bit of notation before we begin. emacs refers to both GNU Emacs by the Free Software Foundation, as well as XEmacs by the XEmacs Project. The emacs major mode ESS[language], where language can take values such as S, SAS, or XLS.
    [Show full text]
  • The Pisharp IDE for Raspberry PI
    http://researchcommons.waikato.ac.nz/ Research Commons at the University of Waikato Copyright Statement: The digital copy of this thesis is protected by the Copyright Act 1994 (New Zealand). The thesis may be consulted by you, provided you comply with the provisions of the Act and the following conditions of use: Any use you make of these documents or images must be for research or private study purposes only, and you may not make them available to any other person. Authors control the copyright of their thesis. You will recognise the author’s right to be identified as the author of the thesis, and due acknowledgement will be made to the author where appropriate. You will obtain the author’s permission before publishing any material from the thesis. The PiSharp IDE for Raspberry PI Bo Si This thesis is submitted in partial fulfillment of the requirements for the Degree of Master of Science at the University of Waikato. August 2017 © 2017 Bo Si Abstract The purpose of the PiSharp project was to build an IDE that is usable for beginners developing XNA-like programs on a Raspberry-Pi. The system developed is capable of 1. Managing and navigating a directory of source files 2. Display a file in a code text editor 3. Display code with syntax highlight 4. Automatically discovering program library structure from code namespaces 5. Compiling libraries and programs automatically with recompilation avoided if source code has not been updated 6. Compiling and running from the IDE 7. Editing more than one file at a time 8.
    [Show full text]
  • Introduction
    1 Introduction A compiler translates source code to assembler or object code for a target machine. A retargetable compiler has multiple targets. Machine-specific compiler parts are isolated in modules that are easily replaced to target different machines. This book describes lcc, a retargetable compiler for ANSI C; it fo- cuses on the implementation. Most compiler texts survey compiling al- gorithms, which leaves room for only a toy compiler. This book leaves the survey to others. It tours most of a practical compiler for full ANSI C, including code generators for three target machines. It gives only enough compiling theory to explain the methods that it uses. 1.1 Literate Programs This book not only describes the implementation of lcc,itis the imple- mentation. The noweb system for “literate programming” generates both the book and the code for lcc from a single source. This source con- sists of interleaved prose and labelled code fragments. The fragments are written in the order that best suits describing the program, namely the order you see in this book, not the order dictated by the C program- ming language. The program noweave accepts the source and produces the book’s typescript, which includes most of the code and all of the text. The program notangle extracts all of the code, in the proper order for compilation. Fragments contain source code and references to other fragments. Fragment definitions are preceded by their labels in angle brackets. For example, the code ≡ a fragment label 1 ĭ2 sum=0; for (i = 0; i < 10; i++) increment sum 1 increment sum 1≡ 1 sum += x[i]; sums the elements of x.
    [Show full text]
  • Literate Programming in Java Section 1 Is Always a Starred Section
    304 TUGboat, Volume 23 (2002), No. 3/4 called limbo; in this case, the introduction.) Most Software & Tools sections consist of a short text part followed by a short code part. Some sections (such as this one) contain only text, some others contain only code. Rambutan: Literate programming in Java Section 1 is always a starred section. That just means it has a title: ‘Computing primes’ in this Prasenjit Saha case. The title is supposed to describe a large group Introduction. Rambutan is a literate program- of consecutive sections, and gets printed at the start and on the page headline. Long programs have ming system for Java with TEX, closely resembling CWEB and the original WEB system.* I developed it many starred sections, which behave like chapter using Norman Ramsey’s Spidery WEB. headings. This article is also the manual, as well as an The source for this section begins example of a Rambutan literate program; that @* Computing primes. This is... is to say, the file Manual.w consists of code and In the source, @* begins a starred section, and any documentation written together in the Rambutan text up to the first period makes up the title. idiom. From this common source, the Rambutan system does two things: 2. This is an ordinary (i.e., unstarred) section, javatangle Manual and its source begins extracts a compilable Java applet to compute the @ This is an ordinary... first N primes, and In the source, @ followed by space or tab or newline javaweave Manual begins an ordinary section. In the next section things get more interesting.
    [Show full text]
  • Literate Programming and Reproducible Research
    JSS Journal of Statistical Software January 2012, Volume 46, Issue 3. http://www.jstatsoft.org/ A Multi-Language Computing Environment for Literate Programming and Reproducible Research Eric Schulte Dan Davison University of New Mexico Counsyl Thomas Dye Carsten Dominik University of Hawai`i University of Amsterdam Abstract We present a new computing environment for authoring mixed natural and com- puter language documents. In this environment a single hierarchically-organized plain text source file may contain a variety of elements such as code in arbitrary program- ming languages, raw data, links to external resources, project management data, working notes, and text for publication. Code fragments may be executed in situ with graphical, numerical and textual output captured or linked in the file. Export to LATEX, HTML, LATEX beamer, DocBook and other formats permits working reports, presentations and manuscripts for publication to be generated from the file. In addition, functioning pure code files can be automatically extracted from the file. This environment is implemented as an extension to the Emacs text editor and provides a rich set of features for authoring both prose and code, as well as sophisticated project management capabilities. Keywords: literate programming, reproducible research, compendium, WEB, Emacs. 1. Introduction There are a variety of settings in which it is desirable to mix prose, code, data, and compu- tational results in a single document. Scientific research increasingly involves the use of computational tools.
    [Show full text]
  • Name Synopsis Description Format of Noweb Files
    NOWEB(1) NOWEB(1) NAME notangle, noweave,nountangle − noweb, a literate-programming tool SYNOPSIS notangle [−Rrootname ...] [−filter command] [−L[format]] [file] ... nountangle [−ml|−m3|−c|−c++|−awk|−tex|−f77|−f90|−lisp|−matlab][−Rrootname ...] [−filter command] [−wwidth] [file] ... noweave [options] [file] ... DESCRIPTION Noweb is a literate-programming tool likeKnuth’s WEB, only simpler.Anoweb file contains program source code interleavedwith documentation. When notangle is givenanoweb file, it writes the program on standard output. When noweave is givenanoweb file, it reads the noweb source and produces, on standard output, LaTeX, TeX, troff,or HTML source for typeset documentation. nountangle converts a literate pro- gram into an ordinary program by turning interleaveddocumentation into comments. The file name ‘−’ refers to standard input. FORMATOFNOWEB FILES A noweb file is a sequence of chunks,which may appear in anyorder.Achunk may contain code or docu- mentation. Documentation chunks begin with a line that starts with an at sign (@) followed by a space or newline. Theyhav e no names. Code chunks begin with <<chunk name>>= on a line by itself. The double left angle bracket (<<) must be in the first column. Chunks are terminated by the beginning of another chunk, or by end of file. If the first line in the file does not mark the beginning of a chunk, it is assumed to be the first line of a documentation chunk. Documentation chunks contain text that is ignored by notangle and copied verbatim to standard output by noweave (except for quoted code). noweave can work with LaTeX,plain TeX, troff or HTML.With plain TeX,itinserts a reference to a TeX macro package, nwmac,which defines commands like \chapter and \section.
    [Show full text]
  • Geany Newsletter #2
    Geany Newsletter #2 Contents 1 About Geany 2 2 Geany Development2 2.1 Update to Scintilla 2.25................................2 2.2 Real-time tag parsing..................................2 2.3 Automatic indentation width detection........................2 2.4 Fixes to template encoding...............................3 3 Plugins 3 3.1 New plugins.......................................3 3.1.1 geanycfp.....................................3 3.2 Significant updates on Split Window Plugin.....................4 3.3 A view onto GeanyVC usage..............................4 4 Let us introduce you...5 4.1 Plugin Focus......................................5 4.1.1 Save Actions...................................5 4.2 Feature Focus......................................7 4.2.1 Append Toolbar to the Menu.........................7 4.2.2 Other screen-space-saving tips.........................7 5 Geany local 8 5.1 Geany at Chemnitzer LinuxTage (March, 19th-20th)................8 6 About this newsletter8 1 1 About Geany Geany is a small and lightweight Integrated Development Environment. It was developed to provide a small and fast IDE, which has only a few dependencies from other packages. Another goal was to be as independent as possible from a special Desktop Environment like KDE or GNOME - Geany only requires the GTK2 runtime libraries. More information about Geany can be found at geany.org. 2 Geany Development 2.1 Update to Scintilla 2.25 With Subversion revision 5682 another update to Scintilla has been done so Geany’s development version is now powered by Scintilla 2.25 in favor of the version previously used: 2.22. As with every update of Scintilla there have been a lot of improvements. This includes changes to Scintilla itself, for example: fixing an issue with marking of a word when double clicking orfixing some memory leaks and unneeded redraws of editor window as well on used lexer e.g.
    [Show full text]