Agda 2

 Table of contents:

 * Installing Agda
 * Configuring the Emacs mode
 * Prerequisites
 * Installing the Epic backend's dependencies
 * Installing a suitable version of Emacs under Windows

 Installing Agda

   Note that this README only discusses installation of Agda, not its
   standard library. See the Agda Wiki for information about the

 There are several ways to install Agda:

 * Using a binary package, prepared for your platform.

   Recommended if such a package exists. See the Agda Wiki.

 * Using a released source package, available from Hackage.

   (Note that if you want to install the development version of Agda,
   then you should use the next method.)

   Install the prerequisites mentioned below, then run the following

     cabal update
     cabal install Agda-executable
     agda-mode setup

   The last command tries to set up Emacs for use with Agda. As an
   alternative you can copy the following text to your .emacs file:

     (load-file (let ((coding-system-for-read 'utf-8))
                     (shell-command-to-string "agda-mode locate")))

 * Using the source tar balls available from the Agda Wiki, or the
   development version of the code available from our darcs repository.

   1)  Install the prerequisites mentioned below.

   2a) Run the following commands in the top-level directory of the
       Agda source tree:

         cabal update
         cabal install
         agda-mode setup
         cd src/main
         cabal install

       The third command tries to set up Emacs for use with Agda. As an
       alternative you can copy the following text to your .emacs file:

         (load-file (let ((coding-system-for-read 'utf-8))
                         (shell-command-to-string "agda-mode locate")))

       If you want to have more control over where files are installed
       then you can give various flags to cabal install, see
       cabal install --help.

   2b) Instead of following 2a you can try to install Agda (including
       batch-mode tool and Emacs mode) by running the following

         make install

 Configuring the Emacs mode

 If you want to you can customise the Emacs mode. Just start Emacs and
 type the following:

    M-x load-library RET agda2-mode RET
    M-x customize-group RET agda2 RET

 This is useful if you want to change the Agda search path, in which
 case you should change the agda2-include-dirs variable.

 If you want some specific settings for the Emacs mode you can add them
 to agda2-mode-hook. For instance, if you do not want to use the Agda
 input method (for writing various symbols like ∀≥ℕ→π⟦⟧) you can add
 the following to your .emacs:

 (add-hook 'agda2-mode-hook
           '(lambda ()
              ; If you do not want to use any input method:
              ; If you want to use the X input method:
              (set-input-method "X")

 Note that, on some systems, the Emacs mode changes the default font of
 the current frame in order to enable many Unicode symbols to be
 displayed. This only works if the right fonts are available, though.
 If you want to turn off this feature, then you should customise the
 agda2-fontset-name variable.


 You need recent versions of the following programs/libraries:

    GNU Emacs:

 You should also make sure that programs installed by cabal-install are
 on your shell's search path.

 For instructions on installing a suitable version of Emacs under
 Windows, see below.

 Non-Windows users need to ensure that the development files for the C
 libraries zlib and ncurses are installed (see and Your package manager may be
 able to install these files for you. For instance, on Debian or Ubuntu
 it should suffice to run

   apt-get install zlib1g-dev libncurses5-dev

 as root to get the correct files installed.

 Installing the Epic backend's dependencies

 The Epic backend is experimental and requires that the Epic program is
 installed. You can install this program by giving the epic flag to

 * When installing from Hackage:

     cabal update
     cabal install Agda -fepic
     cabal install Agda-executable
     agda-mode setup

 * When installing using a source tar ball, following the instructions
   in 2a) above:

     cabal update
     cabal install -fepic
     agda-mode setup
     cd src/main
     cabal install

 * When installing using a source tar ball, following the instructions
   in 2b) above:

     make CABAL_OPTIONS="--global -fepic" install

   (The Makefile specifies CABAL_OPTIONS=--global by default; feel free
   to omit --global.)

 You can also install Epic directly:

   cabal install epic

 Note that Epic depends on other software:

   The Boehm garbage collector:
   The GNU Multiple Precision Arithmetic Library:
   GCC, the GNU Compiler Collection:

 For more information about Epic:

 Installing a suitable version of Emacs under Windows

 Note that Agda code often uses mathematical and other symbols
 available from the Unicode character set. In order to be able to
 display these characters you may want to follow the procedure below
 when installing Emacs under Windows.

 1. Install NTEmacs 22.

    Download from
    the self-extracting executable

    When executed, it asks where to extract itself.  This can be
    anywhere you like, but here we write the top directory for ntemacs as
    in the following.

    What follows is tested only on this version.  Other versions may
    work but you have to figure out yourself how to use Unicode fonts
    on your version.

 2. Install ucs-fonts and mule-fonts for emacs.

    Download from
    the tar file
    Let us write the top directory of extracted files as
    Next we create some derived fonts.
        cd c:/pkg/ucs-fonts/submission
        make all-bdfs
    This gives an error message about missing fonts, but ignore it.

    Download from
    the tar file
    The untarred top directory is named "packages", but we are only
    interested in the subdirectory "packages/fonts".  Let us assume
    we moved this subdirectory to

    Add the following to your .emacs

 ;;;;;;;;; start of quoted elisp code

 (setq bdf-directory-list

 (setq w32-bdf-filename-alist
       (w32-find-bdf-fonts bdf-directory-list))

     chinese-gb2312:-ISAS-Fangsong ti-Medium-R-Normal--16-160-72-72-c-160-GB2312.1980-0,
     " t)

 (setq font-encoding-alist
       (append '(
                 ("JISX0208" (japanese-jisx0208 . 0))
                 ("JISX0212" (japanese-jisx0212 . 0))
                 ("CNS11643.1992.1-0" (chinese-cns11643-1 . 0))
                 ("GB2312" (chinese-gb2312 . 0))
                 ("KSC5601" (korean-ksc5601 . 0))
                 ("VISCII" (vietnamese-viscii-lower . 0))
                 ("MuleArabic-0" (arabic-digit . 0))
                 ("MuleArabic-1" (arabic-1-column . 0))
                 ("MuleArabic-2" (arabic-2-column . 0))
                 ("muleindian-1" (indian-1-column . 0))
                 ("muleindian-2" (indian-2-column . 0))
                 ("MuleTibetan-0" (tibetan . 0))
                 ("MuleTibetan-1" (tibetan-1-column . 0))
                 ) font-encoding-alist))

 ;;;;;;; end of quoted elisp code

    To test the fonts, try

        M-x eval-expression RET
        (set-default-font "fontset-bdf") RET
        M-x view-hello-file

    You should see all the characters without white-boxes.
Page last modified on February 20, 2011, at 06:23 PM
Powered by PmWiki