home.social

#auctex — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #auctex, aggregated by home.social.

  1. @jameshowell @ericsfraga @mstempl @sacha

    I used to know quite well, and used in to write my LaTeX. I've realized that since I started using to write documents, my needed knowledge of LaTeX has dropped about 90%!

  2. @jameshowell @ericsfraga @mstempl @sacha

    I used to know #LaTeX quite well, and used #AucTeX in #emacs to write my LaTeX. I've realized that since I started using #OrgMode to write documents, my needed knowledge of LaTeX has dropped about 90%!

  3. @jameshowell @ericsfraga @mstempl @sacha

    I used to know #LaTeX quite well, and used #AucTeX in #emacs to write my LaTeX. I've realized that since I started using #OrgMode to write documents, my needed knowledge of LaTeX has dropped about 90%!

  4. @jameshowell @ericsfraga @mstempl @sacha

    I used to know #LaTeX quite well, and used #AucTeX in #emacs to write my LaTeX. I've realized that since I started using #OrgMode to write documents, my needed knowledge of LaTeX has dropped about 90%!

  5. @jameshowell @ericsfraga @mstempl @sacha

    I used to know #LaTeX quite well, and used #AucTeX in #emacs to write my LaTeX. I've realized that since I started using #OrgMode to write documents, my needed knowledge of LaTeX has dropped about 90%!

  6. Thinking of revisiting and decluttering my #emacs configuration, little by little. If I carve out the time, I'd love to document the process of finding what I no longer use and tuning the what I already need. Might be fun.

    I mostly use #orgmode #auctex #notmuch #ledgermode. Also do some programming in #python #bash and #c . This might be an exciting opportunity to check out what's up in the emacs world!

  7. Thinking of revisiting and decluttering my #emacs configuration, little by little. If I carve out the time, I'd love to document the process of finding what I no longer use and tuning the what I already need. Might be fun.

    I mostly use #orgmode #auctex #notmuch #ledgermode. Also do some programming in #python #bash and #c . This might be an exciting opportunity to check out what's up in the emacs world!

  8. Thinking of revisiting and decluttering my #emacs configuration, little by little. If I carve out the time, I'd love to document the process of finding what I no longer use and tuning the what I already need. Might be fun.

    I mostly use #orgmode #auctex #notmuch #ledgermode. Also do some programming in #python #bash and #c . This might be an exciting opportunity to check out what's up in the emacs world!

  9. Thinking of revisiting and decluttering my #emacs configuration, little by little. If I carve out the time, I'd love to document the process of finding what I no longer use and tuning the what I already need. Might be fun.

    I mostly use #orgmode #auctex #notmuch #ledgermode. Also do some programming in #python #bash and #c . This might be an exciting opportunity to check out what's up in the emacs world!

  10. Thinking of revisiting and decluttering my #emacs configuration, little by little. If I carve out the time, I'd love to document the process of finding what I no longer use and tuning the what I already need. Might be fun.

    I mostly use #orgmode #auctex #notmuch #ledgermode. Also do some programming in #python #bash and #c . This might be an exciting opportunity to check out what's up in the emacs world!

  11. cursed #emacs #auctex behaviour: It will generate auto files (as in, el files with lists of envs / macros provided by a sty or cls) based on what buffers you have open, even if they are entirely unrelated. That was a bit of a Heisenbug. Also, bc of the way environments are defined in llncs, TeX-auto-generate doesn't recognize them as environments, so I'll have to add them by hand somehow to get completion for C-c C-e

  12. cursed #emacs #auctex behaviour: It will generate auto files (as in, el files with lists of envs / macros provided by a sty or cls) based on what buffers you have open, even if they are entirely unrelated. That was a bit of a Heisenbug. Also, bc of the way environments are defined in llncs, TeX-auto-generate doesn't recognize them as environments, so I'll have to add them by hand somehow to get completion for C-c C-e

  13. cursed #emacs #auctex behaviour: It will generate auto files (as in, el files with lists of envs / macros provided by a sty or cls) based on what buffers you have open, even if they are entirely unrelated. That was a bit of a Heisenbug. Also, bc of the way environments are defined in llncs, TeX-auto-generate doesn't recognize them as environments, so I'll have to add them by hand somehow to get completion for C-c C-e

  14. Ich sehe gerade, dass ich mal wieder vergessen habe, dass hier auf Mastodon – zumindest im Browser – kein #Markdown funktioniert. Vergesse ich immer wieder. Inzwischen steckt es so in mir drin, `\foo` statt \foo zu schreiben, dass auch das in meinen dtx-Dateien immer mal wieder zu einem Fehlerfall führt. Was ich seit einigen Wochen auch ausprobiere ist die automatische Klammerergänzung in #auctex. Die führt allerdings bisher eher zu Klammerfehlern als zu einer Erleichterung.

  15. Ich sehe gerade, dass ich mal wieder vergessen habe, dass hier auf Mastodon – zumindest im Browser – kein #Markdown funktioniert. Vergesse ich immer wieder. Inzwischen steckt es so in mir drin, `\foo` statt \foo zu schreiben, dass auch das in meinen dtx-Dateien immer mal wieder zu einem Fehlerfall führt. Was ich seit einigen Wochen auch ausprobiere ist die automatische Klammerergänzung in #auctex. Die führt allerdings bisher eher zu Klammerfehlern als zu einer Erleichterung.

  16. Ich sehe gerade, dass ich mal wieder vergessen habe, dass hier auf Mastodon – zumindest im Browser – kein #Markdown funktioniert. Vergesse ich immer wieder. Inzwischen steckt es so in mir drin, `\foo` statt \foo zu schreiben, dass auch das in meinen dtx-Dateien immer mal wieder zu einem Fehlerfall führt. Was ich seit einigen Wochen auch ausprobiere ist die automatische Klammerergänzung in #auctex. Die führt allerdings bisher eher zu Klammerfehlern als zu einer Erleichterung.

  17. Ich sehe gerade, dass ich mal wieder vergessen habe, dass hier auf Mastodon – zumindest im Browser – kein #Markdown funktioniert. Vergesse ich immer wieder. Inzwischen steckt es so in mir drin, `\foo` statt \foo zu schreiben, dass auch das in meinen dtx-Dateien immer mal wieder zu einem Fehlerfall führt. Was ich seit einigen Wochen auch ausprobiere ist die automatische Klammerergänzung in #auctex. Die führt allerdings bisher eher zu Klammerfehlern als zu einer Erleichterung.

  18. Ich sehe gerade, dass ich mal wieder vergessen habe, dass hier auf Mastodon – zumindest im Browser – kein #Markdown funktioniert. Vergesse ich immer wieder. Inzwischen steckt es so in mir drin, `\foo` statt \foo zu schreiben, dass auch das in meinen dtx-Dateien immer mal wieder zu einem Fehlerfall führt. Was ich seit einigen Wochen auch ausprobiere ist die automatische Klammerergänzung in #auctex. Die führt allerdings bisher eher zu Klammerfehlern als zu einer Erleichterung.

  19. Hey #emacs user, I need some help.

    Since few days, braces are highlighted in red while I am editing some #texlatex files. Red highlighting is turned off when I save the file. I am using #doomemacs and #auctex. Does someone know how to disable this boring behaviour ?

  20. It feels almost done, except if the point is very close to the end of a footnote. In that case the footnote gets included in the context and so we end up synchronizing with the footnote. I know how to get around this but the easiest way is to use to find the bounds of macros and for the most part pdf-tools doesn't depend on auctex although they cooperate at some points.

  21. It feels almost done, except if the point is very close to the end of a footnote. In that case the footnote gets included in the context and so we end up synchronizing with the footnote. I know how to get around this but the easiest way is to use #auctex to find the bounds of macros and for the most part pdf-tools doesn't depend on auctex although they cooperate at some points.

  22. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  23. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  24. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  25. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  26. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  27. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  28. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  29. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  30. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  31. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  32. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  33. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  34. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  35. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  36. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  37. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  38. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  39. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  40. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  41. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  42. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  43. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  44. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  45. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!

  46. Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Alexander Kozhevnikov (GNU #emacs), Ankit Raj Pandey (GNU #emacs), Artem Iurchenko (GNU #auctex, GNU #emacs), Felix Lechner (GNU #emacs), Giacomo Lorenzetti (GNU #astro), Loïc Lemaître (GNU #emacs), Toshihiro Umehara (GNU #emacs), Zebbediah Beck (GNU #bash) for assigning their copyright to the FSF!