3 ms·

I do not know what temacs is, but on Slackware 15 w/emacs-30.2, temacs does not exist. I wonder if temacs is something used in other operating systems ? I hope

by jmclnx 2mo ago

I do not know what temacs is, but on Slackware 15 w/emacs-30.2, temacs does not exist. I wonder if temacs is something used in other operating systems ? I hope to upgrade to 31.1 on Slackware either today or tomorrow. I will grab the source from Slackware current and compile/install :)

bos 2mo ago
temacs, in older versions of Emacs, is an intermediate build product, never something that is installed. It’s created fairly late during the build, then loaded up with the standard library, undumped, and that is the emacs that is installed.
mickeyp 2mo ago
You typically won't see it installed at all because it's considered an intermediate artefact. You'll have to compile Emacs yourself from source to get it.
jmclnx 2mo ago
Well for what it is worth, I build Emacs 31.1 on Slackware 15.0 and it has an odd issue. I get this message below but issuing that command does not fix it, the warning still appears. So either I need to move from ccrypt to a different encryption utility or revert. For now I will revert and decide if I want to use gnupg instead. I use ccrypt for my password list text file. for more information. * Warning (files): Missing ‘lexical-binding’ cookie in "/usr/share/emacs/site-lisp/ps-ccrypt.el". You can add one with ‘M-x elisp-enable-lexical-binding RET’. See ‘(elisp)Selecting Lisp Dialect’ and ‘(elisp)Converting to Lexical Binding’ for more information. I used the "regular" slackbuild. native-compilation slackbuild fails with a missing library. But Emacs 31.1 is in Slackware Current, so when Slackware is released I will be on it :)
- bygosh 2mo ago
  you should report that bug to ccrypt, emacs is getting a lot more strict about lexical binding support (for good reason). it just needs ;; -- lexical-binding: t/nil -- at the top of the file.

by jmclnx 2mo ago

bos 2mo ago

temacs, in older versions of Emacs, is an intermediate build product, never something that is installed. It’s created fairly late during the build, then loaded up with the standard library, undumped, and that is the emacs that is installed.

mickeyp 2mo ago

You typically won't see it installed at all because it's considered an intermediate artefact. You'll have to compile Emacs yourself from source to get it.

jmclnx 2mo ago

Well for what it is worth, I build Emacs 31.1 on Slackware 15.0 and it has an odd issue. I get this message below but issuing that command does not fix it, the warning still appears. So either I need to move from ccrypt to a different encryption utility or revert. For now I will revert and decide if I want to use gnupg instead. I use ccrypt for my password list text file. for more information. * Warning (files): Missing ‘lexical-binding’ cookie in "/usr/share/emacs/site-lisp/ps-ccrypt.el". You can add one with ‘M-x elisp-enable-lexical-binding RET’. See ‘(elisp)Selecting Lisp Dialect’ and ‘(elisp)Converting to Lexical Binding’ for more information. I used the "regular" slackbuild. native-compilation slackbuild fails with a missing library. But Emacs 31.1 is in Slackware Current, so when Slackware is released I will be on it :)

bygosh 2mo ago
you should report that bug to ccrypt, emacs is getting a lot more strict about lexical binding support (for good reason). it just needs ;; -- lexical-binding: t/nil -- at the top of the file.