Re: [NTG-context] Custom engine settings in AUCTEX

2022-07-02 Thread Lizardo Reyna via ntg-context
You can try adding a TeX-command with this:


(eval-after-load "context"
  '(setq TeX-command-list
(append
  '(
("context"
"context --purgeall %t"
  TeX-run-command t :help "Run context (MarkIV)")
("luametatex"
"context --purgeall %t"
  TeX-run-command t :help "Run context (LMTX)")
  ) TeX-command-list
)
  )
  )

--
Mauricio Reyna


___
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
___


Re: [NTG-context] Guitar chords

2018-08-20 Thread Lizardo Reyna
Thanks for the example, it works!

On 19/08/18 14:29, Wolfgang Schuster wrote:
> \defineruby[song][style=\ss\it,align=flushleft]
> 
> \setupinterlinespace[line=5ex]
> 
> \starttext
> 
> \ruby[song]{Praise}{G} God, \ruby[song]{from}{D} \ruby[song]{Whom}{Em}
> \ruby[song]{all}{Bm} \ruby[song]{bless}{Em}\ruby[song]{ings}{D}
> \ruby[song]{flow}{G};
> 
> \start
> 
> \setupruby[style=\ss\it,align=flushleft]
> 
> \ruby{Praise}{G} Him, all \ruby{crea}{D}\ruby{tures}{Em} \ruby{here}{C}
> \ruby{be}{G}\ruby{low}{D};
> 
> \stop
> 
> \stoptext
> 
> 
> Wolfgang
> 
> 
> Lizardo M. Reyna Bowen schrieb am 19.08.18 um 19:34:
>> Hi,
>> There is a way to put the guitar chords above of a syllable? I have
>> tried with \high{G} command, but it is not the correct form.
>>
>> The result must be similar to this.
>>
>> https://tex.stackexchange.com/questions/104222/songs-package-chord-size
>>
>>
>> Thanks for you help
>>
> 

-- 
Dr. Lizardo M. Reyna Bowen
Profesor
Facultad de Ingeniería Agrícola | Universidad Técnica de Manabí
[Dirección]  Lodana, Santa Ana, Manabí, Ecuador
[Móvil]  +593  982924637
PGP Key: 0xa35a15b90ee64e8d

___
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
___

Re: [NTG-context] Problem of compiling a file with Emacs

2018-08-01 Thread Lizardo Reyna
 pdf (backend for directly generating pdf
> output)mkiv lua stats  > jobdata time: 0.001 seconds saving, 0.000
> seconds loading
> mkiv lua stats  > callbacks: internal: 332, file: 200, direct: 2, late:
> 4, function 577, total: 1115 (1115 per page)
> mkiv lua stats  > loaded patterns: en::2, load time: 0.000
> mkiv lua stats  > result saved in file: Test.pdf, compresslevel 3,
> objectcompresslevel 3
> mkiv lua stats  > loaded fonts: 3 files: latinmodern-math.otf,
> lmroman10-regular.otf, lmroman12-regular.otf
> mkiv lua stats  > font engine: otf 3.104, afm 1.513, tfm 1.000, 9
> instances, 4 shared in backend, 3 common vectors, 1 common hashes, load
> time 0.307 seconds
> mkiv lua stats  > metapost: 0.001 seconds, loading: 0.101, execution:
> 0.000, n: 1, average: 0.102, instances: 1, luacalls: 4, memory: 2.602 M
> mkiv lua stats  > used platform: linux-64, type: unix, binary subtree:
> texmf-linux-64
> mkiv lua stats  > used engine: luatex version 1.08 with functionality
> level 6731, banner: this is luatex, version 1.08.0 (tex live 2018)
> mkiv lua stats  > control sequences: 46515 of 65536 + 10
> mkiv lua stats  > lua properties: engine: lua 5.3, used memory: 96 MB
> (ctx: 96 MB), hash type: lua, hash chars: min(64,40), symbol mask: utf (τεχ)
> mkiv lua stats  > runtime: 0.81 seconds, 2 processed pages, 2 shipped
> pages, 2.469 pages/second
> system  | total runtime: 1.166 seconds
> 
> 
> TeX Output finished at Tue Jul 31 23:45:34
> 
> 
> Fabrice
> 
> 2018-07-31 19:04 GMT+02:00 Lizardo M. Reyna Bowen  <mailto:far...@disroot.org>>:
> 
> I tested the file and conTeXt works well from emacs. The problem
> seems to be related with your conTeXt standalone installation. when
> the file is compiled, emacs create a log buffer  *... output*.  You
> could post that information to look the possible error.
> 
> Have you tried reinstalling conTeXt?
> 
> attached test.pdf
> 
> 
> On 07/31/2018 04:43 AM, Fabrice Couvreur wrote:
>> With (setenv "PATH"
>> "/home/aragorn/texlive/2018/bin/x86_64-linux/context:$PATH" t)  It
>> works properly with C-c C-c
>>
>>
>> With (setenv "PATH"
>> "/home/aragorn/context/tex/texmf-linux-64/bin:$PATH" t) It does
>> not work with C-c C-c
>>
>> The compilation is however correct by using a terminal without
>> Emacs from the standalone version
>> Fabrice
>>
>> 2018-07-31 10:18 GMT+02:00 Fabrice Couvreur
>> mailto:fabrice1.couvr...@gmail.com>>:
>>
>> Hello,
>> I did the same thing as you, but nothing changes. Have you
>> tested the file? The expected result is to have the title of
>> the chapter with the chapter number in large and light gray
>> color. All compiles except the macro that allows to have the
>> chapter number; I get a small rectangle instead.
>> Fabrice
>>
>> 2018-07-30 16:02 GMT+02:00 Lizardo Reyna > <mailto:far...@disroot.org>>:
>>
>>
>> I had a similar issue in emacs few months ago. I use an
>> Ubuntu based
>> GNU/Linux distribution.
>>
>>  My solution was start a new terminal to execute the
>> commands in .bashrc
>> file. When it works, a message will appear in the top of
>> the terminal.
>> "Setting "/home/farliz/context/tex" as ConTeXt root."
>>
>> Then execute emacs from that terminal typing  $ emacs &.
>> This was the
>> only way I got run conTeXt from emacs.
>>
>> I'm not advanced GNU/Linux  user, but there are three
>> configuration
>> files when login; .bashrc, .bash_profile, and .profile. I
>> don't know why
>> this files were not execute automatically when I login, so
>> the path to
>> conTeXt bin is not added and setuptex file is not execute.
>> For this
>> reason it was necessary to start a new terminal.
>>
>> I have my system upgraded and now I don't have problem
>> with that.
>>
>> Regards
>>
>>
>> On 30/07/18 05:45, Fabrice Couvreur wrote:
>> > Hi,
>> > I made the changes that you recommend, but it does not work
>> >
>> > ./emacs
>>