DOCSLIB.ORG

Revisiting WYSIWYG Paradigms for Authoring LATEX

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Revisiting WYSIWYG Paradigms for Authoring LATEX Revisiting WYSIWYG Paradigms for Authoring LATEX David Kastrup Kriemhildstr. 15 44793 Bochum Germany [email protected] Abstract While the command-driven approach of TEX/LATEX has shown its power and flexibility for a variety of purposes, the lack of immediate visual feedback often renders the authoring and reviewing process itself somewhat inconvenient for both beginners and experienced users. The idiosyncratic TEX syntax does not lend itself readily to proofreading and sustained composition where the input syntax differs considerably from the produced results. A number of approaches trying to deal with this frequently perceived short- coming will be illustrated. On the input manipulation side there are tools ranging from a token-based approach (Syntax Highlighting, X-Symbol) to complete ed- itors using LATEX mostly as a means of exporting documents (TEXmacs, LyX). A different range of tools does not aim to provide differences in editing, but fast and convenient access to the output results, mostly in the form of a separate page-oriented preview (Whizzy-TEX, Instant Preview). While the performance of those implementations by now leaves little to be desired, a demand for a tighter coupling of source and preview for editing purposes remains. ‘Source specials’ provide one way for facilitating cross-navigation between source and previews. The preview-latex package (by the author) provides a much closer coupling by directly placing previews of small elements into the source buffer. The Moving Finger writes; and, having writ, Similarity to print: The editing window is sup- Moves on: nor all thy Piety nor Wit posed to resemble the printed output. Shall lure it back to cancel half a Line, Letter shapes: While pixel accuracy is not to be Nor all thy Tears wash out a Word of it. expected, one might at least be able to see the general shape of the letter. Display devices Omar Khayyam´ often offer considerably finer amounts of con- trol for pixel intensity than printing devices do; this makes antialiasing feasible. Antialiasing A The LTEX/WYSIWYG clash tries to compensate for a lower spatial resolu- What is WYSIWYG? WYSIWYG, an acronym tion by varying the brightness of pixels accord- for “what you see is what you get”, is really a mar- ing to the amount of ink that would cover the keting term applied to several different degrees of pixel given higher resolutions. Antialiased let- similarity between the input window and the type- ters tend to be more readable than their non- set output from running a system. antialiased variants, but look rather blurry as In its strictest sense, it means that the typeset the lack of spatial resolution itself is not over- output will be identical to the screen display. Of come, only its impact on the local grayness level course, this goal is ultimately impossible: print de- reduced. vices have different characteristics than the screens Extended character sets: TEX and LATEX itself we are working on: different pixel resolutions, dif- typically use an input representation based on ferent gradation of colors and gray levels. A screen ASCII. While there are extensions in order to be dump from a WYSIWYG type word processor will able to access 8-bit character sets, most mathe- typically look awful compared to a regular printout. matical special characters and operators such as So what are the things people have come to P and R are entered as control sequences such expect from the WYSIWYG moniker? as \sum and \int. WYSIWYG systems usually TUGboat, Volume 23 (2002), No. 1 — Proceedings of the 2002 Annual Meeting 57 David Kastrup ‘closed’ look of the letter shapes itself while still preserving the ‘leading’ characteristic of serifed letters in the overall grayness level. A typical example is lower-case “t” which has a closed bowl when viewed closely, but a distribution of Figure 1: Antialiased Figure 2: Typical stem widths that effectively makes the visual TEX font. screen font. impact of the closing hairline diminish (com- pare figure 1 to the letters in the text of this document). offer a more readable rendition of such charac- Screen resolution is inadequate to properly ters, as well as convenient ways to enter them reflect those visual characteristics. For best leg- without knowing their names. ibility, fonts designed for computer screen usage Non-text elements: The most important items to are to be preferred. mention here would be mathematical formulas Extended character sets: These can lead to an and tables. Those are distinguished by convey- easily implementable improvement in legibility. ing information more directly than possible tex- While the application is straightforward, the tual counterparts. benefits are limited. Line breaks: WYSIWYG word processors typically Non-text elements: These benefit the most from have the same line breaks in the printed output WYSIWYG representations. T X offers consid- as they have on the screen. E erable power for mathematics, and many exten- Pagination: Page breaks and figure positioning are sion packages make use of its macro program- also common elements that WYSIWYG proces- ming features in order to gain additional func- sors will apply to the edited source in the same tionality. For that reason, adequate rendering manner as the resulting output. of compositions like math formulas and tables So where’s the clash? It turns out that some of necessitate considerable programming efforts in those targets are not the best idea for screen-based the editor in order to support them well. An editing and document creation in general, and some appropriate display of those elements is a sig- are at particular odds with the way TEX works: nificant aid for developing a stream of thought, and for copy editing. Similarity to print: TEX is basically a program- ming language. Quite often complicated in- Line breaks and Pagination: TEX finds its line structions lead to the final typesetting results. breaks by paragraph-global optimization, and Editing those in a WYSIWYG manner is hardly employs a process of somewhat localized opti- possible. WYSIWYG tends to hide abomina- mization for finding its page breaks. An in- tions in the input: while text processors such sertion mechanism caters for determining the as Word offer various possibilities to structure proper amounts of additional material (such as your input (format templates, text styles and so footnotes and figures) to attach to a page. All on), this is not immediately apparent in the out- decisions are governed by the evaluation of vari- put. As a result, average users of such systems ous kinds of penalties, and several criteria span- sometimes employ rather abominable means for ning more than one line are employed (visual the formatting of their texts. Not uncommon compatibility of spacing in subsequent lines, ex- is the use of excessive amounts of single spaces tra penalties for adjacent lines ending with hy- for indentation and spacings, and hand adjust- phenated words and so on). ments that are not robust against changes of The non-local layout optimization of TEX is fonts and/or printer. TEX provides an easy way important to achieve the best typeset results. of introducing comments into the typesetting Maintaining this during text entry itself ini- source (% introduces comment lines). Such com- tially appeared infeasible primarily because of ments have no good place in a true WYSIWYG performance considerations (see later for exam- display. ples where this has been mostly overcome). It Letter Shapes: In connection with TEX, the most also can be distracting: the resulting repeated commonly employed fonts are the Computer extensive on-screen text rearrangements result- Modern family by Knuth. Characteristic for ing from small changes in the source make it these fonts is a delicate balance between vari- hard to keep focus on the actual editing loca- ous stem widths and hairlines that produces a tion. 58 TUGboat, Volume 23 (2002), No. 1 — Proceedings of the 2002 Annual Meeting Revisiting WYSIWYG Paradigms for Authoring LATEX ument, the constant fervor with which paragraphs get adjusted and shifted while single letters are be- ing typed is about as useful and convenient as con- stantly busy window cleaners on a construction site. LyX Similar to TEXmacs, LyX is a complete word processor. In contrast to TEXmacs, however, LyX promotes the WYSIWYM (What You See is What You Mean) buzzphrase instead of WYSIWYG. In earlier versions of LyX, this was mostly a euphemism for ‘what you see is somewhat reminiscent of what you will get’, but in more recent versions a lot of work has been invested to make the display indeed show additional information about the underlying structure of the document. Since LyX is not bound to have the input’s appearance match the output, it can generously apply colors for outlining structural Figure 3: Screenshot from TEXmacs window. details, and use push buttons and similar graphic elements impacting the editing window layout for Various systems bridging the gap indicating footnotes and cross references. TEXmacs The word processor TEXmacs is about the clearest demonstration about what a full imple- mentation of the WYSIWYG paradigm could look like for TEX. While TEXmacs does not make use of TEX itself nor offers convenient access to TEX packages and programming, it employs TEX typeset- ting algorithms and fonts (antialiased on screen) for its operation. The printed rendition of the pages is quite the same as the screen representation (though having your editing window paginated is optional). It does not support LATEX as a native format, but exports to it (needing a special style file) and, con- siderably less reliably, also imports from it. Its key- bindings are reminiscent of Emacs’ keybindings, and it will interpret quite a few macro sequences intro- duced with backslash. The editor can be extended Figure 4: Typical LyX display.
Load more

Recommended publications
  • Build It with Nitrogen the Fast-Off-The-Block Erlang Web Framework
    Build it with Nitrogen The fast-off-the-block Erlang web framework Lloyd R. Prentice & Jesse Gumm dedicated to: Laurie, love of my life— Lloyd Jackie, my best half — Jesse and to: Rusty Klophaus and other giants of Open Source— LRP & JG Contents I. Frying Pan to Fire5 1. You want me to build what?7 2. Enter the lion’s den9 2.1. The big picture........................ 10 2.2. Install Nitrogen........................ 11 2.3. Lay of the land........................ 13 II. Projects 19 3. nitroBoard I 21 3.1. Plan of attack......................... 21 3.2. Create a new project..................... 23 3.3. Prototype welcome page................... 27 3.4. Anatomy of a page...................... 30 3.5. Anatomy of a route...................... 33 3.6. Anatomy of a template.................... 34 3.7. Elements............................ 35 3.8. Actions............................. 38 3.9. Triggers and Targets..................... 39 3.10. Enough theory........................ 40 i 3.11. Visitors............................ 44 3.12. Styling............................. 64 3.13. Debugging........................... 66 3.14. What you’ve learned..................... 66 3.15. Think and do......................... 68 4. nitroBoard II 69 4.1. Plan of attack......................... 69 4.2. Associates........................... 70 4.3. I am in/I am out....................... 78 4.4. Styling............................. 81 4.5. What you’ve learned..................... 82 4.6. Think and do......................... 82 5. A Simple Login System 83 5.1. Getting Started........................ 83 5.2. Dependencies......................... 84 5.2.1. Rebar Dependency: erlpass ............. 84 5.3. The index page........................ 85 5.4. Creating an account..................... 87 5.4.1. db_login module................... 89 5.5. The login form........................ 91 5.5.1.
    [Show full text]
  • LYX Frequently Asked Questions with Answers
    LYX Frequently Asked Questions with Answers by the LYX Team∗ January 20, 2008 Abstract This is the list of Frequently Asked Questions for LYX, the Open Source document processor that provides a What-You-See-Is-What-You-Mean environment for producing high quality documents. For further help, you may wish to contact the LYX User Group mailing list at [email protected] after you have read through the docs. Contents 1 Introduction and General Information 3 1.1 What is LYX? ......................... 3 1.2 That's ne, but is it useful? . 3 1.3 Where do I start? . 4 1.4 Does LYX run on my computer? . 5 1.5 How much hard disk space does LYX need? . 5 1.6 Is LYX really Open Source? . 5 2 Internet Resources 5 2.1 Where should I look on the World Wide Web for LYX stu? 5 2.2 Where can I get LYX material by FTP? . 6 2.3 What mailing lists are there? . 6 2.4 Are the mailing lists archived anywhere? . 6 2.5 Okay, wise guy! Where are they archived? . 6 3 Compatibility with other word/document processors 6 3.1 Can I read/write LATEX les? . 6 3.2 Can I read/write Word les? . 7 3.3 Can I read/write HTML les? . 7 4 Obtaining and Compiling LYX 7 4.1 What do I need? . 7 4.2 How do I compile it? . 8 4.3 I hate compiling. Where are precompiled binaries? . 8 ∗If you have comments or error corrections, please send them to the LYX Documentation mailing list, <[email protected]>.
    [Show full text]
  • Bringing GNU Emacs to Native Code
    Bringing GNU Emacs to Native Code Andrea Corallo Luca Nassi Nicola Manca [email protected] [email protected] [email protected] CNR-SPIN Genoa, Italy ABSTRACT such a long-standing project. Although this makes it didactic, some Emacs Lisp (Elisp) is the Lisp dialect used by the Emacs text editor limitations prevent the current implementation of Emacs Lisp to family. GNU Emacs can currently execute Elisp code either inter- be appealing for broader use. In this context, performance issues preted or byte-interpreted after it has been compiled to byte-code. represent the main bottleneck, which can be broken down in three In this work we discuss the implementation of an optimizing com- main sub-problems: piler approach for Elisp targeting native code. The native compiler • lack of true multi-threading support, employs the byte-compiler’s internal representation as input and • garbage collection speed, exploits libgccjit to achieve code generation using the GNU Com- • code execution speed. piler Collection (GCC) infrastructure. Generated executables are From now on we will focus on the last of these issues, which con- stored as binary files and can be loaded and unloaded dynamically. stitutes the topic of this work. Most of the functionality of the compiler is written in Elisp itself, The current implementation traditionally approaches the prob- including several optimization passes, paired with a C back-end lem of code execution speed in two ways: to interface with the GNU Emacs core and libgccjit. Though still a work in progress, our implementation is able to bootstrap a func- • Implementing a large number of performance-sensitive prim- tional Emacs and compile all lexically scoped Elisp files, including itive functions (also known as subr) in C.
    [Show full text]
  • A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine
    Graduate Theses, Dissertations, and Problem Reports 2012 A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine Daniel Sloan West Virginia University Follow this and additional works at: https://researchrepository.wvu.edu/etd Recommended Citation Sloan, Daniel, "A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine" (2012). Graduate Theses, Dissertations, and Problem Reports. 4919. https://researchrepository.wvu.edu/etd/4919 This Thesis is protected by copyright and/or related rights. It has been brought to you by the The Research Repository @ WVU with permission from the rights-holder(s). You are free to use this Thesis in any way that is permitted by the copyright and related rights legislation that applies to your use. For other uses you must obtain permission from the rights-holder(s) directly, unless additional rights are indicated by a Creative Commons license in the record and/ or on the work itself. This Thesis has been accepted for inclusion in WVU Graduate Theses, Dissertations, and Problem Reports collection by an authorized administrator of The Research Repository @ WVU. For more information, please contact [email protected]. A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine Daniel Sloan Thesis submitted to the College of Engineering and Mineral Resources at West Virginia University in partial fulfillment of the requirements for the degree of Master of Science in Computer Science Yenumula V. Reddy, Ph.D., Chair Bojan Cukic, Ph.D. Cynthia D. Tanner, MS. Lane Department of Computer Science and Electrical Engineering Morgantown, West Virginia 2012 Keywords: Work-patterns, file usage, semantic desktop, machine learning Copyright c 2012 Daniel Sloan Abstract A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine Daniel Sloan A work pattern, also known as a usage pattern, can be broadly defined as the methods by which a user typically utilizes a particular system.
    [Show full text]
  • Emacspeak User's Guide
    Emacspeak User's Guide Jennifer Jobst Revision History Revision 1.3 July 24,2002 Revised by: SDS Updated the maintainer of this document to Sharon Snider, corrected links, and converted to HTML Revision 1.2 December 3, 2001 Revised by: JEJ Changed license to GFDL Revision 1.1 November 12, 2001 Revised by: JEJ Revision 1.0 DRAFT October 19, 2001 Revised by: JEJ This document helps Emacspeak users become familiar with Emacs as an audio desktop and provides tutorials on many common tasks and the Emacs applications available to perform those tasks. Emacspeak User's Guide Table of Contents 1. Legal Notice.....................................................................................................................................................1 2. Introduction.....................................................................................................................................................2 2.1. What is Emacspeak?.........................................................................................................................2 2.2. About this tutorial.............................................................................................................................2 3. Before you begin..............................................................................................................................................3 3.1. Getting started with Emacs and Emacspeak.....................................................................................3 3.2. Emacs Command Conventions.........................................................................................................3
    [Show full text]
  • Metadefender Core V4.12.2
    MetaDefender Core v4.12.2 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
    [Show full text]
  • Emacs Speaks Statistics (ESS): a Multi-Platform, Multi-Package Intelligent Environment for Statistical Analysis
    Emacs Speaks Statistics (ESS): A multi-platform, multi-package intelligent environment for statistical analysis A.J. Rossini Richard M. Heiberger Rodney A. Sparapani Martin Machler¨ Kurt Hornik ∗ Date: 2003/10/22 17:34:04 Revision: 1.255 Abstract Computer programming is an important component of statistics research and data analysis. This skill is necessary for using sophisticated statistical packages as well as for writing custom software for data analysis. Emacs Speaks Statistics (ESS) provides an intelligent and consistent interface between the user and software. ESS interfaces with SAS, S-PLUS, R, and other statistics packages under the Unix, Microsoft Windows, and Apple Mac operating systems. ESS extends the Emacs text editor and uses its many features to streamline the creation and use of statistical software. ESS understands the syntax for each data analysis language it works with and provides consistent display and editing features across packages. ESS assists in the interactive or batch execution by the statistics packages of statements written in their languages. Some statistics packages can be run as a subprocess of Emacs, allowing the user to work directly from the editor and thereby retain a consistent and constant look- and-feel. We discuss how ESS works and how it increases statistical programming efficiency. Keywords: Data Analysis, Programming, S, SAS, S-PLUS, R, XLISPSTAT,STATA, BUGS, Open Source Software, Cross-platform User Interface. ∗A.J. Rossini is Research Assistant Professor in the Department of Biostatistics, University of Washington and Joint Assis- tant Member at the Fred Hutchinson Cancer Research Center, Seattle, WA, USA mailto:[email protected]; Richard M.
    [Show full text]
  • 52. What Is Binary • Language That Hardware Uses to Communicate
    Language that hardware uses to communicate Digital images are made up of little dots of colour 52. What is Binary Made of 1’s and 0’s - 1 means on and data is present 57. Pixels called pixels and 0 means off and no data is present Image resolution describes the quality of an image. It tells 53. Binary Table 128 64 32 16 8 4 2 1 58. Image Resolution us how many pixels there are in an image. The higher the number, the better the image quality is. The letter A is represented by the number 65 Image resolution is measure in pixels per inch 128 64 32 16 8 4 2 1 For short, this is written as ppi 54. A in Binary 59. Pixels per Inch 0 1 0 0 0 0 0 1 Sometimes, it is referred to as dpi and this is short for dots So A is 01000001 per inch C = 67 60. High Resolution Because high resolution images contain more pixels per inch 128 64 32 16 8 4 2 1 Images – Good Points they can create very good quality images 0 1 0 0 0 0 1 1 Because high resolution images contain more pixels per inch a = 97 55. Text to Binary 61. High Resolution they hold a lot of data. 128 64 32 16 8 4 2 1 Images – Bad Points The bad point of a high resolution image is that they can Converting the 0 1 1 0 0 0 0 1 often take up a lot of storage space word Cat to Binary t = 116 128 64 32 16 8 4 2 1 Because they do not contain as many pixels per inch as high 62.
    [Show full text]
  • WYSIWYG Editor OU Campus V10
    WYSIWYG Editor OU Campus v10 OmniUpdate, Inc. 1320 Flynn Road, Suite 100 Camarillo, CA 93012 OmniUpdate, Inc. 1320 Flynn Road, Suite 100 Camarillo, CA 93012 800.362.2605 805.484.9428 (fax) www.omniupdate.com Copyright ® 2014 OmniUpdate, Inc. All rights reserved. Document Number: b-003 Publish Date: 7/16/2014 ® OmniUpdate and OU Campus™ are trademarks or registered trademarks of OmniUpdate, Inc. Any other company and product names, and trademarks mentioned within are property of their respective owners. Content is subject to change without notice. About OmniUpdate, Inc. ® OmniUpdate is the leading web content management system (CMS) provider for higher education. The company focuses on providing an exceptional product and customer experience to its OU Campus™ CMS users who manage more than 700 web and mobile sites in the U.S. and around the world. OU Campus is secure and scalable, server and platform independent, and seamlessly integrates with other enterprise campus systems. It provides college and university web developers, administrators, and marketers with the user- friendly tools and deployment flexibility they need to achieve excellence. For more information, visit . About This Guide The WYSIWYG Editor document provides a PDF version of the Support Site topics regarding the usage of the WYSIWYG Editor and the tools available for it. OU Campus Support The Support site is available to everyone and users are encouraged to visit and browse the site for information. An institution's administrators are also available if the answer cannot be found on the Support site or further explanation and clarification is needed. Administrators may contact the OmniUpdate Support Team.
    [Show full text]
  • 1 What Is Gimp? 3 2 Default Short Cuts and Dynamic Keybinding 9
    GUM The Gimp User Manual version 1.0.0 Karin Kylander & Olof S Kylander legalities Legalities The Gimp user manual may be reproduced and distributed, subject to the fol- lowing conditions: Copyright © 1997 1998 by Karin Kylander Copyright © 1998 by Olof S Kylander E-mail: [email protected] (summer 98 [email protected]) The Gimp User Manual is an open document; you may reproduce it under the terms of the Graphic Documentation Project Copying Licence (aka GDPL) as published by Frozenriver. This document is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANT- ABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the Graphic Documentation Project Copying License for more details. GRAPHIC DOCUMENTATION PROJECT COPYING LICENSE The following copyright license applies to all works by the Graphic Docu- mentation Project. Please read the license carefully---it is similar to the GNU General Public License, but there are several conditions in it that differ from what you may be used to. The Graphic Documentation Project manuals may be reproduced and distrib- uted in whole, subject to the following conditions: The Gimp User Manual Page i Legalities All Graphic Documentation Project manuals are copyrighted by their respective authors. THEY ARE NOT IN THE PUBLIC DOMAIN. • The copyright notice above and this permission notice must be preserved complete. • All work done under the Graphic Documentation Project Copying License must be available in source code for anyone who wants to obtain it. The source code for a work means the preferred form of the work for making modifications to it.
    [Show full text]
  • An Introduction to ESS + Xemacs for Windows Users of R
    An Introduction to ESS + XEmacs for Windows Users of R John Fox∗ McMaster University Revised: 23 January 2005 1WhyUseESS+XEmacs? Emacs is a powerful and widely used programmer’s editor. One of the principal attractions of Emacs is its programmability: Emacs can be adapted to provide customized support for program- ming languages, including such features as delimiter (e.g., parenthesis) matching, syntax highlight- ing, debugging, and version control. The ESS (“Emacs Speaks Statistics”) package provides such customization for several common statistical computing packages and programming environments, including the S family of languages (R and various versions of S-PLUS), SAS, and Stata, among others. The current document introduces the use of ESS with R running under Microsoft Windows. For some Unix/Linux users, Emacs is more a way of life than an editor: It is possible to do almost everything from within Emacs, including, of course, programming, but also writing documents in mark-up languages such as HTML and LATEX; reading and writing email; interacting with the Unix shell; web browsing; and so on. I expect that this kind of generalized use of Emacs will not be attractive to most Windows users, who will prefer to use familiar, and specialized, tools for most of these tasks. There are several versions of the Emacs editor, the two most common of which are GNU Emacs, a product of the Free Software Foundation, and XEmacs, an offshoot of GNU Emacs. Both of these implementations are free and are available for most computing platforms, including Windows. In my opinion, based only on limited experience, XEmacs offers certain advantages to Windows users, such as easier installation, and so I will explain the use of ESS under this version of the Emacs editor.1 As I am writing this, there are several Windows programming editors that have been customized for use with R.
    [Show full text]
  • Texing in Emacs Them
    30 TUGboat, Volume 39 (2018), No. 1 TEXing in Emacs them. I used a simple criterion: Emacs had a nice tutorial, and Vim apparently did not (at that time). Marcin Borkowski I wince at the very thought I might have chosen Abstract wrong! And so it went. I started with reading the In this paper I describe how I use GNU Emacs to manual [8]. As a student, I had a lot of free time work with LAT X. It is not a comprehensive survey E on my hands, so I basically read most of it. (I still of what can be done, but rather a subjective story recommend that to people who want to use Emacs about my personal usage. seriously.) I noticed that Emacs had a nice TEX In 2017, I gave a presentation [1] during the joint mode built-in, but also remembered from one of GUST/TUG conference at Bachotek. I talked about the BachoTEXs that other people had put together my experiences typesetting a journal (Wiadomo´sci something called AUCTEX, which was a TEX-mode Matematyczne, a journal of the Polish Mathematical on steroids. Society), and how I utilized LAT X and GNU Emacs E In the previous paragraph, I mentioned modes. in my workflow. After submitting my paper to the In order to understand what an Emacs mode is, let proceedings issue of TUGboat, Karl Berry asked me me explain what this whole Emacs thing is about. whether I'd like to prepare a paper about using Emacs with LATEX. 1 Basics of Emacs Well, I jumped at the proposal.
    [Show full text]