ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vladimir Lomov <lomov.vl@yandex.ru>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Emacs + latest beta
Date: Fri, 24 Aug 2018 21:48:27 +0800	[thread overview]
Message-ID: <20180824134827.GD762@smoon.vl-lomov.ru> (raw)
In-Reply-To: <CACyK-er4upgyWUpP=ZMOeH0b3qi=iD8YwQeoXwn0oyvQcJUtJw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2844 bytes --]

Hello,
** Fabrice Couvreur [2018-08-24 12:31:19 +0200]:

> Hi Vladimir,
> Thanks for everything, it seems to work !

> You are the only one who knew how to solve the problem.

> Here is the content of my ~./emacs file that you probably need to improve :
> 
> -------------------------------- 8< ---------------------------------
> 
> (eval-after-load "context"
>   '(setq TeX-command-list
>      (cons '("ConTeXt"
> "PATH=/home/aragorn/context/tex/texmf-linux-64/bin:$PATH context %s"
>        TeX-run-command nil t :help "Run context (MarkIV)")
> TeX-command-list))
> )
> 
> (setq ConTeXt-mode-hook
>       (lambda () (setq TeX-command-extra-options "--purgeall")))
> 
> 
> (add-hook 'ConTeXt-mode-hook
>           (lambda()
>             (setq TeX-command-default "ConTeXt Full")))

Why did you set "ConTeXt Full" as your default command? The above
'setq' introduces "ConTeXt" command to process a context file. When I
said that everything is OK I meant that I did C-c C-c, checked that in
minibuffer the "ConTeXt" command is chosen and then hit Enter.

> -------------------------------- 8< ---------------------------------
> 
> By cons if I add this :
> 
> -------------------------------- 8< ---------------------------------
> 
> (setenv "TEXMFCNF" nil)
> (setenv "TEXROOT" "/home/aragorn/context/tex")
> (setenv "TEXMFCACHE" (format "%s/.cache" (getenv "HOME")))
> 
> 
> -------------------------------- 8< ---------------------------------
> 
> 
>  the compilation returns a damaged pdf file that I can not open.

I don't know why you get "damaged" pdf file (in fact how do you know
that file is damaged?) but "TEXMFCNF" is special variable that I uses to
tweak TeX Live configuration for my latex workflow but context
(standalone and from TL) refuses to work if this variable is set (in
terminal I do 'unset' while in Emacs I set its value to 'nil' because
this is identical to "unset" it). The "TEXROOT" variable I found in
update script, I'm not sure if context requires it to work but IMHO, it
is harmless. And the last variable "TEXMFCACHE" I use to force context
to use ~/.cache for "luatex-cache" directory and not "pollute" my home
directory (without it the "luatex-cache" directory will be created in
$HOME directory).

> I installed texlive 2018 and context standalone in my home directory and
> emacs in the /usr/share/emacs directory with Arch Linux ; can that explain
> my problems ?

Not sure but I'll wait you answer about "ConTeXt Full" vs "ConTeXt" I
mentioned above.

> Fabrice

[...]

---
WBR, Vladimir Lomov

-- 
I'm serious about thinking through all the possibilities before we
settle on anything.  All things have the advantages of their
disadvantages, and vice versa.
             -- Larry Wall in <199709032332.QAA21669@wall.org>

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2018-08-24 13:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 11:05 Fabrice Couvreur
2018-08-22 12:30 ` Vladimir Lomov
2018-08-23  8:48   ` Fabrice Couvreur
2018-08-24  2:20     ` Vladimir Lomov
2018-08-24 10:31       ` Fabrice Couvreur
2018-08-24 13:48         ` Vladimir Lomov [this message]
2018-08-24 14:39           ` Hans Hagen
2018-08-27  3:57             ` Vladimir Lomov
2018-08-24 23:23           ` Fabrice Couvreur
2018-08-27  4:07             ` Vladimir Lomov
2018-08-27  9:51               ` Fabrice Couvreur
2018-08-27 13:47                 ` Fabrice Couvreur
2018-08-28  5:57                   ` Vladimir Lomov
2018-08-28  9:18                     ` Fabrice Couvreur
2018-08-29  2:58                       ` Vladimir Lomov
2018-08-29  9:39                         ` Fabrice Couvreur
2018-08-29 10:01                           ` Fabrice Couvreur
2018-08-29 14:12                             ` Vladimir Lomov
2018-08-30 17:13                               ` Fabrice Couvreur
2018-08-29 14:01                           ` Vladimir Lomov
2018-08-27 14:35                 ` Aditya Mahajan
2018-08-27 15:13                   ` Fabrice Couvreur
2018-08-23 18:58 ` Wolfgang Schuster
2018-08-24  1:29   ` Vladimir Lomov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180824134827.GD762@smoon.vl-lomov.ru \
    --to=lomov.vl@yandex.ru \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).