DOCSLIB.ORG

IC Documentation Release 0.1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IC Documentation Release 0.1 IC Documentation Release 0.1 IC team Sep 27, 2021 Contents 1 How to contribute to IC 3 1.1 Prepare github..............................................3 1.2 Prepare your repositories.........................................3 1.3 Use a higher-level git interface......................................3 1.4 History philosophy............................................4 1.5 Workflow summary...........................................4 1.6 Workflow in detail............................................5 1.7 Testing..................................................8 1.8 Style guide................................................9 2 How to use notebooks in IC 11 2.1 The problem with notebooks....................................... 11 2.2 Workflow................................................. 11 3 Core modules 13 4 Indices and tables 15 i ii IC Documentation, Release 0.1 Contents: Contents 1 IC Documentation, Release 0.1 2 Contents CHAPTER 1 How to contribute to IC 1.1 Prepare github • Get a github account if you do not already have one. • Upload your SSH key, if you have not already done so. 1.2 Prepare your repositories TODO • Fork the IC repository • Clone your fork • set nextic as upstream 1.3 Use a higher-level git interface Do yourself a favour, and use magit to interact with git: it’s the best git UI on the planet. Even if you don’t use or dislike Emacs, use magit, and think of Emacs as the GUI framework in which magit is written. You will enjoy and learn to understand git much more if you use magit. [Editor’s note: Seriously, I tried to find something to recommend for those who don’t use Emacs. It wasted a lot of my time, and I came to the conclusion that recommending anything else would be a waste of your time. Just use magit.] To make the magit experience even better, use helm. 3 IC Documentation, Release 0.1 1.4 History philosophy In the words of Ben Sandofsky: Treat public history as immutable, atomic, and easy to follow. Treat private history as disposable and malleable. The intended workflow is: 1. Create a private branch off a public branch. 2. Regularly commit your work to this private branch. 3. Once your code is perfect, clean up its history. 4. Merge the cleaned-up branch back into the public branch. • In IC, step 4 is done by the IC administators after the work has been reviewed and approved, so you don’t have to worry about this step for now. • The history that appears in your local clone (your private history) is there entirely for your benefit. As such, it is malleable and disposable, and you can modify it however and whenever you like. • The history that appears in the central nextic repository serves as a clean, high-level description of the evolution of the project, where – it should be easy to find where and when something was changed, added, removed, where bugs were introduded (perhaps using tools such as git bisect), – a high-level description of the changes should be available. As such, the central history should – be linear, – contain very descriptive commit messages describing and documenting the changes. • The commits that appear in your fork on github can serve a number of purposes: – A place from which you submit pull requests, asking for your contribution to be incorporated into the main repository. (The commits that appear in pull requests should therefore conform to the high standards required by the main history: clean, linear (usually squashed) and documented with descriptive commit messages.) – Triggers of travis builds, checking that your work builds and passes all the tests in a clean environment. – Sharing your work with other developers and collaborating on development with others before submitting a pull request. 1.5 Workflow summary 1. Create a topic branch starting at upstream/master in your local repo. 2. Make numerous checkpoint commits to your topic branch. 3. Write tests for the code you write. 4. Push the topic branch to your github fork (origin) whenever you want feedback from Travis. 5. In preparation for making a pull request (PR), squash the checkpoint commits into a smaller number of logically self-contained commits with descriptive, high-level commit messages. Try to make each commit (and its diff) tell a story that will be easily understood by the reviewers. 6. Fetch (whatever you do, do not pull) upstream/master into your local repository.. 4 Chapter 1. How to contribute to IC IC Documentation, Release 0.1 7. Rebase your topic branch onto upstream/master. 8. Push the branch to origin. 9. a pull request (PR) from your github page. 10. Wait for the PR to be approved and merged. 11. Fetch upstream/master into your local repo. 12. Delete your topic branch, both locally and in your fork. 13. GOTO 1 1.6 Workflow in detail In what follows, the commands required to achieve the effect will be given in two styles (eventually; initially the git CLIs are likely to be TODOs). 1. magit 2. git command line interface (CLI) In the case of magit you should type the instructions in some magit buffer inside Emacs. If no such buffer is visible, create the magit status buffer with M-x magit-status. This last command must be given in some buffer linked to a file or directory inside the relevant git repository. Magit buffers can usually be closed with q. Emacs commands in general can be interrupted with C-g. In the case of the git CLI, you should type the commands in a shell whose working directory is inside there relevant git repository. 1. Before starting some new work, make sure that you have the most recent IC code. • magit: f e upstream RET – f opens the magit fetching popup – e allows you to specify the remote from which you would elike to fetch – upstream specifies that you want to fetch from the central nextic repository. (This assumes that you have already added upstream as a remote pointing at nextic/IC in your local repository) • git CLI: git fetch upstream 2. Create a topic branch. In the following examples replace ‘topic’ with whatever name you want to give to your branch. The name sohuld be meaningful to you and identify the work that you are doing. You may end up having multiple topic branches in existence simultaneously, so picking good names will make life easier for you. • magit: b c upstream/master RET topic RET – b opens the magit branch popup – c creates and checks out a new branch – upstream/master is the location from which you want to branch off – topic is the name of your new branch • git CLI: git checkout -b topic upstream/master 1.6. Workflow in detail 5 IC Documentation, Release 0.1 Magit will walk you through these steps interactively. Helm, if you’ve installed it, will improve the interactive experience. If you make a mistake magit will help you avoid digging yourself into a deeper hole. With the git CLI you are on your own. 3. Create plenty of checkpoint commits while you are working. Frequent checkpoint commits ensure that, if you ever get yourself into a complete mess, you can get out of it cheaply by reverting to a recent sensible state. This is how to do a local commit • magit: – M-x magit-status (or your keybinding, possibly C-x g) Opens the magit status buffer, showing you (among other things) * which files have been modified since the last commit * which files have been deleted since the last commit * which files exist but are not registered in the repository The most useful keys inside this buffer are * s: stage - include this in the next commit * u: unstage - undo a previous stage * n: next - move to the next interesting location * p: previous - move to the previous interesting location * c: commit - start the commit process * d: diff - open the magit diff popup So, you should specify what you want to be included in the commit by staging it. Then proceed with the commit with c, at which point a commit message buffer should appear, with self-explanatory comments inside it. In short, write a commit message and then perform the commit with C-c C-c. When you get around to creating a pull request, you should squash (see below) your checkpoint com- mit messages into a smaller number of coherent, clean, commits with descriptive commit messages describing your work. The purpose of the checkpoint commit messages is to make authoring the pull request commit messages as easy as possible. • git CLI: TODO 4. Make sure that the code you contribute is adequately tested. See below. 5. Whenever you want to see whether your current code builds and passes all the required tests in a clean environ- ment, commit (described above) and push to your fork (origin). • magit: – The first time in a new branch: P p origin RET – Thereafter: P p P opens the magit push popup. Once there, p pushes to the remote which needs to be set once for each branch. • git CLI: TODO 6. Once you have achieved something worth incorporating into the main repository, it’s time to make a pull request (PR). Usually your pull request should consist of a smaller number of commits than you originally made during development, each with a carefully written, high-level, descriptive commit message describing your work. The commit message of a single-commit PR is taken as the default PR description text. If your PR contains more than one commit, you should create a description of the whole collection in the GitHub PR interface. 6 Chapter 1. How to contribute to IC IC Documentation, Release 0.1 You should squash your numerous checkpoint commits to make cleaner PR commits.
Load more

Recommended publications
  • Emacspeak — the Complete Audio Desktop User Manual
    Emacspeak | The Complete Audio Desktop User Manual T. V. Raman Last Updated: 19 November 2016 Copyright c 1994{2016 T. V. Raman. All Rights Reserved. Permission is granted to make and distribute verbatim copies of this manual without charge provided the copyright notice and this permission notice are preserved on all copies. Short Contents Emacspeak :::::::::::::::::::::::::::::::::::::::::::::: 1 1 Copyright ::::::::::::::::::::::::::::::::::::::::::: 2 2 Announcing Emacspeak Manual 2nd Edition As An Open Source Project ::::::::::::::::::::::::::::::::::::::::::::: 3 3 Background :::::::::::::::::::::::::::::::::::::::::: 4 4 Introduction ::::::::::::::::::::::::::::::::::::::::: 6 5 Installation Instructions :::::::::::::::::::::::::::::::: 7 6 Basic Usage. ::::::::::::::::::::::::::::::::::::::::: 9 7 The Emacspeak Audio Desktop. :::::::::::::::::::::::: 19 8 Voice Lock :::::::::::::::::::::::::::::::::::::::::: 22 9 Using Online Help With Emacspeak. :::::::::::::::::::: 24 10 Emacs Packages. ::::::::::::::::::::::::::::::::::::: 26 11 Running Terminal Based Applications. ::::::::::::::::::: 45 12 Emacspeak Commands And Options::::::::::::::::::::: 49 13 Emacspeak Keyboard Commands. :::::::::::::::::::::: 361 14 TTS Servers ::::::::::::::::::::::::::::::::::::::: 362 15 Acknowledgments.::::::::::::::::::::::::::::::::::: 366 16 Concept Index :::::::::::::::::::::::::::::::::::::: 367 17 Key Index ::::::::::::::::::::::::::::::::::::::::: 368 Table of Contents Emacspeak :::::::::::::::::::::::::::::::::::::::::: 1 1 Copyright :::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Emacs + Magit = Git Magic
    Emacs + Magit = Git Magic Shakthi Kannan Version 1.0 GNU FDL Shakthi Kannan Emacs + Magit = Git Magic Initialization M-x magit-status Open magit buffer Shakthi Kannan Emacs + Magit = Git Magic Buffers $ Actual git command executed g Update magit status Shakthi Kannan Emacs + Magit = Git Magic Section Visibility TAB Toggle current section S-TAB Toggle visibility of current children 1-4 Shows four levels of a section M-f1-4g Shows four levels af ALL sections Shakthi Kannan Emacs + Magit = Git Magic Untracked files s Add untracked file to staging area C-u S Stage all untracked and tracked files i Add filename to .gitignore k Delete untracked file, forever Shakthi Kannan Emacs + Magit = Git Magic Staging and Committing u Unstage C-u s Prompt file for staging S Move all hunks to stage U Unstage everything that has been staged c Pop buffer for commit message C-c C-c Amend commit message C-c C-k Erase magit-log-edit buffer and bury it Shakthi Kannan Emacs + Magit = Git Magic History l l History of current head in terse form l L History in verbose form RET More info on commit in new buffer v Revert the current commit C-w Copy sha1 to kill ring . Mark commit = Difference between current commit and marked Shakthi Kannan Emacs + Magit = Git Magic Reflog l h Browse reflog Shakthi Kannan Emacs + Magit = Git Magic Diffing d Difference between working tree and another revision D Difference between any two arbitrary revisions Shakthi Kannan Emacs + Magit = Git Magic Tagging t t Create lightweight tag t a Create annotated tag Shakthi Kannan Emacs + Magit = Git Magic Resetting
    [Show full text]
  • Emacs – Beating the Learning Curve from Zero to Lightspeed
    Emacs – Beating the Learning Curve From Zero to Lightspeed. Timo Bingmann August 18, 2015 Contents 1 Overview 2 2 Most Important Key Chords 2 2.1 When Things Go Wrong . 2 2.2 Meta-X . 3 2.3 Move Around in Text . 3 2.4 Mark, Copy, and Paste Text . 3 2.5 Open File into Buffers . 3 2.6 Switching Buffers (Open Files) . 4 2.7 Organizing Buffers into Frames and Windows . 4 2.8 Search and Replace . 4 2.9 Change Font Size . 4 3 Advanced Text Editing 4 3.1 Rectangle Copy/Paste . 5 3.2 Keyboard Macros . 5 3.3 Run Shell Commands . 5 3.4 Multiple Cursors . 5 4 Directory Listings (dired) 5 4.1 Give Me a Terminal, NOW! . 6 4.2 Tramp Mode . 6 5 Customization 6 6 Source code editing 7 7 C/C++ Projects 7 7.1 Identifier Expansion . 7 7.2 Snippets . 7 7.3 Semantics Jumps . 8 7.4 Ede (Cedet) Projects . 8 7.5 Grep and Ag . 8 7.6 Bookmarks . 8 7.7 ecb - Emacs Code Browser . 8 7.8 TODO Tag Browsing . 9 1 7.9 gdb inside emacs. 9 8 Magit - Git Magic! 9 9 Editing LATEX 10 10 org-mode 10 11 evil-mode 11 1 Overview This is a quick and dirty emacs tutorial. It does not feature the most flashy features or goodies. Instead, it focuses on solid day-to-day efficiency features. It is probably best to print out this tutorial, grab a version of emacs, and start reading and trying out each command in this manual from top to bottom.
    [Show full text]
  • 1.2 (Obsolete)
    Magit User Manual for version 1.2 (obsolete) The Magit Project Developers Copyright c 2008-2015 The Magit Project Developers Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. i Table of Contents 1 Introduction::::::::::::::::::::::::::::::::::::: 1 2 Acknowledgments::::::::::::::::::::::::::::::: 2 3 Sections:::::::::::::::::::::::::::::::::::::::::: 3 4 Status:::::::::::::::::::::::::::::::::::::::::::: 4 5 Untracked files :::::::::::::::::::::::::::::::::: 5 6 Staging and Committing ::::::::::::::::::::::: 6 7 History :::::::::::::::::::::::::::::::::::::::::: 8 8 Reflogs::::::::::::::::::::::::::::::::::::::::::: 9 9 Commit Buffer::::::::::::::::::::::::::::::::: 10 10 Diffing::::::::::::::::::::::::::::::::::::::::: 11 11 Tagging ::::::::::::::::::::::::::::::::::::::: 12 12 Resetting ::::::::::::::::::::::::::::::::::::: 13 13 Stashing::::::::::::::::::::::::::::::::::::::: 14 14 Branching::::::::::::::::::::::::::::::::::::: 15 15 The Branch Manager :::::::::::::::::::::::: 16 16 Wazzup ::::::::::::::::::::::::::::::::::::::: 17 17 Merging ::::::::::::::::::::::::::::::::::::::: 18 18 Rebasing :::::::::::::::::::::::::::::::::::::: 19 ii 19 Interactive Rebasing ::::::::::::::::::::::::: 20 20 Rewriting ::::::::::::::::::::::::::::::::::::: 21 21 Pushing and Pulling ::::::::::::::::::::::::: 22 22 Submodules:::::::::::::::::::::::::::::::::::
    [Show full text]
  • Magit Reference Card
    Magit Reference Card Getting help in Emacs C-h k 〈key〉 describe function bound to 〈key〉 C-h b list the current key-bindings for the focus buffer C-h m describe mode C-h l show the keys you have pressed 〈prefix〉 C-h show all key-bindings beginning with 〈prefix〉 Section Movement Section Visibility p previous section n next section TAB toggle visibility of current section P previous sibling section C-TAB cycle visibility of section and children N next sibling section M-TAB cycle visibility of diff-related sections ˆ parent section S-TAB cycle visibility of all sections in buffer Staging Status/Diff/Log Buffer s stage change at point SPC update commit/diff buffer or scroll up u unstage change at point DEL update commit/diff buffer or scroll down S stage all changes in worktree h show dispatch popup U reset index to some commit g refresh M-x magit-unstage-all remove all changes G refresh all M-x magit-stage-file stage current file q bury current buffer M-x magit-unstage-file unstage current file L toggle margin x soft reset (hard when argument is given) View Git Output y show references (tags and branches) Y cherry $ display process buffer for current repository C-c C-b move backward in buffer’s history k kill process represented by section at point C-c C-f move forward in buffer’s history Popups ! running git f fetching o submoduling b branching F pulling r rebasing B bisecting l logging w apply patches c committing m merging W format patches d diffing M remoting t tagging E ediff P pushing z stashing Status/Diff/Log Buffer References Buffer y compare references
    [Show full text]
  • )'S Tired Eto Ove Smdei ;Big,B{ in Doul Ladwolj Bt
    •' '• V - ' ''i V 'ik ; ' . 1 'r. -.'i ■ Ijtaforsptied Aiibthilieriw oFdjyi jE SS,D l H ^r^a Nelson leajads area ■ e p ric e : ■ f e r s into. s ta te5 mI eet. elections. OfOll eVev e r " ■ . :'SpORTS,Ci S^PMKEis ^ b p Clltilim bing? MW e s - N e W i ceirints H ........ .............. i p t f m n nbillvieto ovesmdeiin doulbt when.lawmakers sent the! mnsslver reserved for “We will have to rcpass ihele w hole H o u s e ^ t t ^ n i M ^ a i n m easu re to th e W hite House ' unopposed leg- thing,thlr as will tiie Senate,” saliaid Hep. lytopassfarn T h a t m e a n s Dush vetoedla t d i..- in s id e islation. The LouiseLot Slaughter. D-N.Y. "WtiVc can't t j ''' - '' ■'•:\^ ■-' * ' entent bill from the one CcCongress ^rm bill illwill Senate was lellet thi e farm bill just die." 5 t ^ * s ^ t a t e < l P ^ ' •' 3 1 6 -i0 8 v o te,le, Bush had vetoed the passed,pai raising questions tlthat the help afeasugaiifiar expcclcd to foi- TheWliltcT House, almost glgleeful- fiv^ycar'mealeasure, saying Jt waf. too eventualcvc law would be uncciconstltu- beet growers.rs. low suit. The Iy,ly.s seized on the fumble and sjsaid the ::W ASHiNGTON^ Th«T he -H ouse expensive ,aiand''gave-too' much tional.tlpi Republicans objecteited w hen -------------------— correct version mix-upmb coiild give Congressi limli e to bvcrwhymih^y.'rcjeciedfd 1P resident' m o n ey to wiwealthy farmers when DemocratsDe proposed passisslng the SeoPagoOl>1 would then bc fixfixi tlic “bloated” bill.
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • Full Stack Lisp Build and Deploy Modern Lisp Applications
    Full Stack Lisp Build and deploy modern Lisp applications Pavel Penev This book is for sale at http://leanpub.com/fullstacklisp This version was published on 2016-05-30 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License Tweet This Book! Please help Pavel Penev by spreading the word about this book on Twitter! The suggested hashtag for this book is #FullStackLisp. Find out what other people are saying about the book by clicking on this link to search for this hashtag on Twitter: https://twitter.com/search?q=#FullStackLisp CONTENTS Contents Warning to early readers ..................................... i Current Status ......................................... i What remains to be written .................................. ii Additional ideas ........................................ ii Thank you! ........................................... ii About ................................................ iii Introduction ............................................ iv Prerequisites ............................................ v Typographic conventions ..................................... vi Part One: Development environment .............. 1 Chapter 1: Roswell ........................................ 2
    [Show full text]
  • Flycheck Release 32-Cvs
    Flycheck Release 32-cvs Aug 25, 2021 Contents 1 Try out 3 2 The User Guide 5 2.1 Installation................................................5 2.2 Quickstart................................................7 2.3 Troubleshooting.............................................8 2.4 Check buffers............................................... 12 2.5 Syntax checkers............................................. 14 2.6 See errors in buffers........................................... 18 2.7 List all errors............................................... 22 2.8 Interact with errors............................................ 24 2.9 Flycheck versus Flymake........................................ 27 3 The Community Guide 33 3.1 Flycheck Code of Conduct........................................ 33 3.2 Recommended extensions........................................ 34 3.3 Get help................................................. 37 3.4 People.................................................. 37 4 The Developer Guide 45 4.1 Developer’s Guide............................................ 45 5 The Contributor Guide 51 5.1 Contributor’s Guide........................................... 51 5.2 Style Guide................................................ 54 5.3 Maintainer’s Guide............................................ 57 6 Indices and Tables 63 6.1 Supported Languages.......................................... 63 6.2 Glossary................................................. 85 6.3 Changes................................................. 85 7 Licensing 93 7.1 Flycheck
    [Show full text]
  • Ag.El Documentation Release 0.45
    ag.el Documentation Release 0.45 Wilfred Hughes Feb 25, 2018 Contents 1 Installation 3 1.1 Operating System............................................3 1.2 Emacs..................................................3 1.3 Ag....................................................3 1.4 Ag.el...................................................3 2 Usage 5 2.1 Running a search.............................................5 2.2 The results buffer.............................................5 2.3 Search for file names...........................................6 3 Configuration 7 3.1 Highlighting results...........................................7 3.2 Path to the ag executable.........................................7 3.3 Visiting the results............................................8 3.4 Overriding the arguments passed to ag..................................8 3.5 Hooks...................................................8 3.6 Multiple search buffers..........................................8 4 Extensions 9 4.1 Using with Projectile...........................................9 4.2 Customising the project root.......................................9 4.3 Editing the results inline.........................................9 4.4 Focusing and filtering the results.....................................9 4.5 Writing Your Own............................................9 5 Developing ag.el 11 5.1 Using flycheck (optional)........................................ 11 6 Changelog 13 6.1 Previous Versions............................................ 13 6.2 master.................................................
    [Show full text]
  • GNU Hyperbole Manual
    GNU Hyperbole Manual The Everyday Hypertextual Information Manager Bob Weiner This manual is for GNU Hyperbole (Edition 7.1.3, Published August, 2020). Copyright c 1989-2020 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation. GNU Hyperbole sofware is distributed under the terms of the GNU General Public License version 3 or later, as published by the Free Software Foundation, Inc. GNU Hyperbole is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY, without even the implied warranty of MERCHANTABIL- ITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details in the file, \COPYING", within the Hyperbole package directory. Published by the Free Software Foundation, Inc. Author: Bob Weiner E-mail: <[email protected]> (This is a mail list). Web: www.gnu.org/software/hyperbole The body of the manual was written in Emacs and laid out using the GNU Texinfo markup language. i Short Contents GNU Hyperbole :::::::::::::::::::::::::::::::::::::::::: 1 1 Introduction :::::::::::::::::::::::::::::::::::::::::: 2 2 Smart Keys :::::::::::::::::::::::::::::::::::::::::: 7 3 Buttons :::::::::::::::::::::::::::::::::::::::::::: 18 4 Menus:::::::::::::::::::::::::::::::::::::::::::::: 38 5 HyControl :::::::::::::::::::::::::::::::::::::::::: 42 6 Koutliner ::::::::::::::::::::::::::::::::::::::::::: 47 7 HyRolo :::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Reconsidering Constitutional Formation I National Sovereignty a Comparative Analysis of the Juridification by Constitution Studies in the History of Law and Justice
    Studies in the History of Law and Justice 6 Series Editors: Georges Martyn · Mortimer Sellers Ulrike Müßig Editor Reconsidering Constitutional Formation I National Sovereignty A Comparative Analysis of the Juridification by Constitution Studies in the History of Law and Justice Volume 6 Series editors Georges Martyn University of Ghent , Gent , Belgium Mortimer Sellers University of Baltimore , Baltimore , Maryland, USA Editorial Board António Pedro Barbas Homem, Universidade de Lisboa Emanuele Conte, Università degli Studi Roma Tre Gigliola di Renzo Villata, Università degli Studi di Milano Markus Dirk Dubber, University of Toronto William Ewald, University of Pennsylvania Law School Igor Filippov, Moscow State University Amalia Kessler, Stanford University Mia Korpiola, Helsinki Collegium for Advanced Studies Aniceto Masferrer, Universidad de Valencia Yasutomo Morigiwa, Nagoya University Graduate School of Law Ulrike Muessig, Universität Passau Sylvain Soleil, Université de Rennes James Q.Whitman, Yale Law School The purpose of this book series is to publish high quality volumes on the history of law and justice. Legal history can be a deeply provocative and infl uential fi eld, as illustrated by the growth of the European universities and the ius commune, the French Revolution, the American Revolution, and indeed all the great movements for national liberation through law. The study of history gives scholars and reformers the models and cour- age to question entrenched injustices, by demonstrating the contingency of law and other social arrangements. Yet legal history today fi nds itself diminished in the universities and legal academy. Too often scholarship betrays no knowledge of what went before, or why legal institutions took the shape they did.
    [Show full text]