coq-club AT inria.fr
Subject: The Coq mailing list
List archive
- From: Zhaohui Li <lizhaohui1991 AT gmail.com>
- To: coq-club AT inria.fr
- Subject: [Coq-Club] A new coq-project-file feature based on PG
- Date: Sat, 24 Sep 2016 11:53:57 +0800
- Authentication-results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=lizhaohui1991 AT gmail.com; spf=Pass smtp.mailfrom=lizhaohui1991 AT gmail.com; spf=None smtp.helo=postmaster AT mail-io0-f172.google.com
- Ironport-phdr: 9a23:XChuGhSg+GPFzyDBX8dphvYgrNpsv+yvbD5Q0YIujvd0So/mwa64ZxWN2/xhgRfzUJnB7Loc0qyN4vqmAT1Lvs3JmUtBWaQEbwUCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnYsExnyfTB4Ov7yUtaLyZ/mjabqqtaMOE1hv3mUWftKNhK4rAHc5IE9oLBJDeIP8CbPuWZCYO9MxGlldhq5lhf44dqsrtY4q3wD86Fpy8kVWqLjOq88ULZwDTI8Mmlz6te4mwPESF695nIbUngX2j5JS1zB7QP6V5Dxryqj57sk8CafNMzyC7szXGLxvO9QVBb0hXJfZHYC+2bNh5kogQ==
Hello everyone.
I have implemented a new coq-project-file feature based on proof-general.
The differences compared to the old _PROJECT file are that:
1. New project-file can specify both coq version and coq arguments,
so we can have different coq implementations with different projects.
2. New project-file uses elisp language. Actually, it is just .el file.
For example, in a project, my project-file is this:
(setq coq-prog-name (expand-file-name "coqtop" (getenv "coq85bin")))
(setq coq-prog-args `("-R" ,(file-name-directory (buffer-file-name)) "Certi"))
This means I need coq8.5 and using the project-file directory as the root coq
LoadPath.
3. Don't like old _PROJECT file and emacs .dir-locals.el file, which will be loaded
each time opening a coq file, new project-file is read only before we want run a
coq file.
Because in my experience, I always run coq file in a project, but need to see files
in another project, which project-file should not be read to overwrite the running one.
I write this feature without touching proof-general's code, and the original purpose is
only for my own use:)
Is anyone think this useful?
Thanks ~
I have implemented a new coq-project-file feature based on proof-general.
The differences compared to the old _PROJECT file are that:
1. New project-file can specify both coq version and coq arguments,
so we can have different coq implementations with different projects.
2. New project-file uses elisp language. Actually, it is just .el file.
For example, in a project, my project-file is this:
(setq coq-prog-name (expand-file-name "coqtop" (getenv "coq85bin")))
(setq coq-prog-args `("-R" ,(file-name-directory (buffer-file-name)) "Certi"))
This means I need coq8.5 and using the project-file directory as the root coq
LoadPath.
3. Don't like old _PROJECT file and emacs .dir-locals.el file, which will be loaded
each time opening a coq file, new project-file is read only before we want run a
coq file.
Because in my experience, I always run coq file in a project, but need to see files
in another project, which project-file should not be read to overwrite the running one.
I write this feature without touching proof-general's code, and the original purpose is
only for my own use:)
Is anyone think this useful?
Thanks ~
- [Coq-Club] A new coq-project-file feature based on PG, Zhaohui Li, 09/24/2016
- [Coq-Club] A new coq-project-file feature based on PG, Pierre Courtieu, 09/25/2016
- Re: [Coq-Club] A new coq-project-file feature based on PG, Zhaohui Li, 09/26/2016
- [Coq-Club] A new coq-project-file feature based on PG, Pierre Courtieu, 09/25/2016
Archive powered by MHonArc 2.6.18.