Emacs

Some time ago I mentioned a very peculiar type of TODOs I’d like to implement. These are things I’d like to do from time to time, but not necessarily on a regular basis...

Hello everyone! My first post in this new forum.

I read a lot for research, and to keep track of the read books I am experimenting with a combination of bibtex and org mode column view. I have list of my books in an org-file, which then is exported to a bib-file to be able to use org-cite-insert.

Now, to filter the list of books to show I need to set the :match criteria in the column view dynamic block. This works well for all exact matches. But for instance, if I want to match all the books I have read in a certain year (I have a field in the per-book-heading like: DATE_FINISHED), I cannot filter them out. If the value is, say, 2023-08-26, how can I filter that when I am looking only for the year?

It seems to me, :match is always looking at the whole entry, I cannot use:

:match "DATE_FINISHED=\"2023\"

I would have to use:

:match "DATE_FINISHED=\"2023-08-26\"

But I want all the books of 2023, not only those of the 26th of August. How could I solve this? Thank you very much for any hint!

Titus

I mentioned in a previous post that one of the things that I'm doing to bootstrap the content on this community was to get submissions from reddit and place them here.

I couldn't resist and decided to play with Reddit's and Lemmy's API to see if I could automate some of this job (not on Elisp, I will shamefully admit) and after some time I got a Python script that I checks the date of the last submission and grabs the url of all new (non-self) submissions and posts them here.

I was wondering what the community thinks of the idea of me running this script every hour or so? This would basically mean that every post from reddit would be synchonized here.

There are some other things that I'd like to do as well:

• avoid posting links from people who are already here (to let them make the Lemmy post themselves)
• Lots of posts on /r/emacs are "self" posts from people describing or summarizing their project/blog posts, and with a link inside it. I'd like to add a (interactive) step to look at "self" submissions and see if there is a link that can be submitted.
• While checking for "self" submissions, possibly send a DM to the poster inviting them to join this community

What do you think? Should I go forward with these ideas?

b'\n \n

\n

\n \n \n \n

\n

• PozberovÃ(C) spracovanie
  \n \n \n

  • PríjmovÃ(C)\n dopravníky \n

  • Výklopníky\n paliet \n

  • Odhliňovače a\n predtriediče \n

  • KefovÃ(C) čističky \n

  • Práčky a poliÅ¡Ã(C)ry \n

  • InÅ¡pekčnÃ(C) stoly \n

  • Plniče paliet \n

  • Plniče big-bagov \n \n

\n

• Váženie a balenie\n \n

  • KombinačnÃ(C) váhy \n

  • Priame váhy \n

  • AutomatickÃ(C) baliace stroje \n

  • RekonÅ¡trukcie váh a\n baličiek \n

  • Referencie \n \n

\n

• Automatizácia a PLC \n

• Skladovanie\n \n

  • Vzduchotechnika v\n paletových skladoch \n

  • Vzduchotechnika\n vo voľne ložených skladoch \n

  • Riadenie senníkov \n \n

\n

• Prospekty \n

\n \n \n

\n

\n \n \n

Compiling GNU Emacs 30 on Debian 12

\n \n \n

\n

\n

\n

\n \n

\n

\n \n \n

Prologue

\n\t

\n\t In this blog, I'll show you how to compile Emacs on\nGNU/Linux Debian 12. But the procedure is of course easily adaptable\nto any GNU/Linux OS, since we'll only be installing a few packages\nusing their package manager. To make everything tutti , we will also\n\t add a native compiler and tree-sitter.\n
\n

Native compilation

\na€¦in Emacs is the process of translating and converting Emacs Lisp source code to machine code, which allows Emacs Lisp to run more efficiently and faster each time it is run.\n
\nNative compilation in Emacs is not a new feature; it was introduced in version 28.1.\n
\nThe result of native compilation is a binary blob that (can) be subsequently loaded when Emacs starts.\n
\n
\n

Tree-sitter

\n\nTree-sitter is a syntax tree analysis library used to parse code as it\nis manipulated. It is a tool that allows you to analyze the syntax\nstructure of a programming language and provides an interface to\nperform various operations such as code refactoring, dependency\nvisualization, or documentation generation.\n\nTree-sitter supports different programming languages and allows users\nto define their own "recipes".\n\nNormally, when working with code (meaning highlighting it, folding it,\nmoving it to definitions,a€¦) some kind of parser working with regular\nexpressions was used.\n\nTree-sitter (supposedly) provides better parsing than a regular\nexpression parser. Regular expressions work with characters or a group\nof characters, and these must appear in the displayed text in a\ndefined order. However, a tree-sitter is capable of parsing and\nrecognizing more complex patterns of structured language, including\nsyntax.\n\nThe regular expression parser requires that the entire input text be\nread and processed at once, which is memory and computing power\nintensive when dealing with large files. Tree-sitter works\nincrementally and performs parsing without the need to load the entire\ntext at once.\n\nThe regular expression parser only works with the linear structure of\nthe text and cannot capture its hierarchy. Tree-sitter is able to\nunderstand the hierarchical structure of the text and provide\ninformation about different levels of structure - such as nested code\nblocks and so on.\n
\n
\n

Installation

\n
\n

Installing the necessary tools and libraries

\n\nTo successfully compile GNU Emacs, we will need some additional tools\nand libraries that may not be present in a normal OS installation.\n\n \n\nThese are:\n\n

\n| git              | tool for storing, managing and tracking changes to project source code                                |\n| autoconf         | (simplified) used to generate a Makefile file for compilation                                         |\n| texinfo          | tool for working with and converting documentation                                                    |\n| gnutls-bin       | libraries for using SSL/TLS protocols (if we want to use Emacs as a mail client)                      |\n| libgccjit-12-dev | library containing the language independent JIT (Just-In-Time) compiler needed for native compilation |\n| gcc              | is probably not necessary to introduce the C compiler                                                 |\n| libgtk2.0-dev    | GTK libraries if Emacs is to run in its own rendered window and not in the terminal                   |\n| libgnutls28-dev  | libraries for compiling for gnutls-bin                                                                |\n| libxpm-dev       | libraries to support xpm graphics filesknižnice pre podporu xpm grafických súborov                    |\n| libgif-dev       | a€¦ and detto for gif                                                                                   |\n| libtinfo-dev     | transition package for libncurses                                                                     |\n

\n
\nWithout hesitation or second thoughts 😏, we copy the command:\n

\n  sudo apt install git autoconf make texinfo gnutls-bin libgccjit-12-dev gcc libgtk2.0-dev libgnutls28-dev lib libxpm-dev libgif-dev

\n

\n\n

Tree-sitter

\n\nAccording to the tutorial on [Mastering Emacs: How to Get Started with Tree-Sitter](https://www.masteringemacs.org/article/how-to-get-started-tree- sitter):\n
\nDownload the latest version of tree-sitter:\n\n

\n  git clone https://github.com/tree-sitter/tree-sitter.git

\n
\nAnd compile the program using the familiar three-line magic:\n
\n

\n  cd tree-sitter/\n  make\n  sudo make install\n

\n
\nAnd (if we haven't already) if we define one more variable so that Emacs doesn't fiddle during starting up:\n

\n  export LD_LIBRARY_PATH=/usr/local/lib/\n

\n
\n\n

GNU Emacs 30

\n\nFrom the savannah repositories we'll download the Emacs source code:\n

\n  git clone -b master git://git.sv.gnu.org/emacs.git\n

\n
\nNext up:\n

\n  cd emacs\n

\n
\nRun autogen.sh , which is used to generate configuration files and scripts for compilation and installation\n
\n

\n  ./autogen.sh\n

\n
\nAnd then we run configure , with parameters\nfor tree-sitter support and native compilation. \n\n
\n

\n  ./configure --with-tree-sitter --with-native-compilation --with-mailutils --with-pop\n

\n\n( --with-pop - if we also require POP3 protocol when downloading emails)\n
\n \nFollowed by the classic:\n

\n  make\n  sudo make install\n

\n
\n

Tree-sitter setting

\n
\n\nSomewhere in the initialization file, we put a list of addresses from where the rules for that language can be downloaded:\n

\n  (setq treesit-language-source-alist\n    \'((bash "https://github.com/tree-sitter/tree-sitter-bash"))\n     (cmake "https://github.com/uyha/tree-sitter-cmake")\n     (c "https://github.com/tree-sitter/tree-sitter-c")\n     (css "https://github.com/tree-sitter/tree-sitter-css")\n     (elisp "https://github.com/Wilfred/tree-sitter-elisp")\n     (go "https://github.com/tree-sitter/tree-sitter-go")\n     (html "https://github.com/tree-sitter/tree-sitter-html")\n     (javascript "https://github.com/tree-sitter/tree-sitter-javascript" "master" "src")\n     (json "https://github.com/tree-sitter/tree-sitter-json")\n     (make "https://github.com/alemuller/tree-sitter-make")\n     (markdown "https://github.com/ikatyang/tree-sitter-markdown")\n     (python "https://github.com/tree-sitter/tree-sitter-python")\n     (toml "https://github.com/tree-sitter/tree-sitter-toml")\n     (tsx "https://github.com/tree-sitter/tree-sitter-typescript" "master" "tsx/src")\n     (typescript "https://github.com/tree-sitter/tree-sitter-typescript" "master" "typescript/src")\n     (yaml "https://github.com/ikatyang/tree-sitter-yaml")))\n

\n
\nAnd run the\n

\n  M-x treesit-install-language-grammar\n

command.\n
\n
\n\nWell, we have compiled Emacs in versiona€¦ well, last version, for me it was testing version 30.\n\nBut I haven't deployed it to full operation yet.\n\n\t

\n\t
\nA couple of pictures at the end:\n

\n

\n Fig. 1: Installed version 30 \n

\n\n Fig. 2: ts-c-mode \n\n\n\n\t\n

\n

\n \n

\n

\n \n

\n

\n \n \n

O našej spoločnosti

\n NaÅ¡a firma TRITON FAMME s.r.o., ako nasledovník firiem TRITON\n a FAMME pôsobí na trhu od roku 2005 (firma FAMME od roku\n 1996). Orientujeme sa na predaj poľnohospodárskej, lesníckej a\n komunálnej techniky, na návrhy, realizáciu prípadne\n rekonÅ¡trukcie technologických liniek na pozberovÃ(C) spracovanie\n zemiakov spolu so skladovými technológiami na Slovensku i v\n zahraničí.
\n Vykonávame tiež servisnú činnosÅ¥ technologických liniek, nielen\n na Slovensku, ale aj v okolitých krajinách, a v krajinách\n bývalÃ(C)ho Sovietskeho zväzu. \n

\n \n

\n

• ObchodnÃ(C) meno spoločnosti:
  \n

\n

• IČO: \n

• DIČ / IČ DPH \n

\n \n \n

\n

• Triton Famme s.r.o.
  \n

\n

• 48 320 404 \n \n

  • 2120129781 / SK2120129781 \n \n

\n \n

\n \n

\n

\n \n \n

Kontaktujte nás

\n pre viac informácií a poradenstvo \n

\n

• Sídlo Levočská 862/28,
  \n 058 01 Poprad

\n \n

* Kancelária JilemnickÃ(C)ho\n 307/77  

\n 059 51 Veľká Lomnica

\n \n

• E-mail triton (zav.)\n famme.sk \n

• Telefóny Richard Fabo:\n +421 905 829 763
  \n Miroslav Fabo: +421 905 381 924

\n

\n \n

\n

\n \n

Design: TEMPLATED\n Images: Unsplash (CC0)\n

\n

\n

\n

\n \n'

What are you using to make your VHDL development faster and cleaner; eMacs configurations files / linters etc.

This is a followup on the previous call for collecting GC statistics [1].

We now got around 90 reports in the mailing list [2] and the frequency of getting new reports is fairly low now.

Thus, I would like to make one final call to submit the statistics. After a week from now, I will start bringing all the data together.

[1] https://reddit.com/r/emacs/comments/14dej62/please_help_collecting_statistics_to_optimize/

[2] https://lists.gnu.org/archive/html/emacs-gc-stats/

URL: https://bbb.emacsverse.org/b/iho-h7r-qg8-led Time & Date: <2023-08-09 Wed 19:00-21:00 @+03,Europe/Istanbul>

Thanks everyone who participated! We had quite a few people by Emacs meetup standards.

Here is a short summary of the main discussion points (those that I remember):

• Adham Omran announced his new package for Anki (flash card/spaced repetition) integration: https://github.com/adham-omran/ankifier Efficiently create Anki flashcards from your notes.

• Ilya Cheryshov announced his new package to display agenda time grid as interactive svg image. Looks like the usual Google calendar view, but inside Emacs. https://github.com/ichernyshovvv/org-timeblock/ Org mailing list discussion: https://list.orgmode.org/87edkc85fl.fsf@localhost/T/#t

  • Similar, but ASCII-only package: https://github.com/ml729/calfw-blocks, based on Calfw Emacs calendar framework.

• More on visualizing Org statistics:

  • https://github.com/rksm/clj-org-analyzer/: clocking data visualizer using web-frontend. Features heatmap view of clocking time per-day. Allows filtering by tags.
  • https://github.com/Elilif/org-heatmap/: monthly heatmap for habit tracking
  • A bit tangent, but illustrates how to make use of time clocking: https://samplesize.one/blog/posts/my_year_in_data/
    • One more article I did not mention during the meetup: https://sqrtminusone.xyz/posts/2023-04-13-emacs/

• [[info:eintr#Top][eintr#Top]] Elisp introduction for non-programmers. This is really a well-written manual worth reading if your config is larger than a few lines.

• yantar92's window manager: Awesome WM https://awesomewm.org/

• https://git.sr.ht/~bzg/worg is the source code of Org WIKI (WORG) [ Contributions welcome: a number of articles really need some love there ]

  • We also have some Org internals documented as articles in WORG.

• Meeting report export template (backend): https://github.com/DarkBuffalo/ox-report which reminded me of actual LaTeX template by Tecosaur (Org dev): https://github.com/tecosaur/BMC

• New WIP fast LaTeX preview system with instant preview as you type

  • Demo: https://www.youtube.com/watch?v=n-AfvuV-bYo
  • Another demo previously posted on the mailing list: https://www.youtube.com/watch?v=n-AfvuV-bYo
  • And the mailing list discussion with more details: https://list.orgmode.org/orgmode/87lek2up0w.fsf@tec.tecosaur.net/

• =#+begin_src := will give you completion of header arguments

  • Same for #+ keywords and, sometimes, for their values (like for #+TAGS: )
  • The underlying code is in lisp/org-pcomplete.el
  • Also, see org-eldoc (part of org-contrib): https://git.sr.ht/~bzg/org-contrib/tree/master/item/lisp/org-eldoc.el

• Collaboration using Org mode

  • Concurrent editing options are not great, unfortunately:
    • https://code.librehq.com/qhong/crdt.el (need Emacs for all sides)
    • https://logseq.com/: similar to notion/obsidian, but supports Org syntax
  • Can use Git, if not real-time. Org is just a plain text.
  • I also used email workflow using pdf export -> sending email -> getting pdf with comments back -> modifying Org source -> ...

• Authoring books/thesis in Org

  • Adham Omran wrote his thesis in Arabic using Org mode
    • Emacs has built-in right-to-left language support [[info:emacs#Bidirectional Editing][emacs#Bidirectional Editing]]
    • Right-to-left may be mixed with left-to-right (English) in Org export, though some LaTeX-specific tweaking may be needed.
      • Org offers some help with #+LANGUAGE document keyword (see [[info:org#LaTeX specific export settings][org#LaTeX specific export settings]])
    • Also, https://list.orgmode.org/orgmode/87h6z7jq4o.fsf@localhost/
    • There was a question about XeLaTeX, but, AFAIK, event normal LaTeX can support Arabic and other Unicode languages with polyglossia package. Although fonts may be tricky to set and a number of people opt-in to LuaTeX/XeLaTeX for smoother experience (the downside is that non-LaTeX may not always be an option in real-life publisher requirements)
    • Examples from Org mailing list on complex typesetting while keeping sources in Org mode
      • https://list.orgmode.org/orgmode/87y1yovcip.fsf@posteo.net/
      • The bi-lingual book I mentioned: https://list.orgmode.org/orgmode/87h70tyyiz.fsf@posteo.net/

• Adham Omran wrote colemak input method for Arabic (only qwerty-based variant is available by default in Emacs)

  • I suggested submitting it as a patch for Emacs core.

• On the Emacs fringe indicators showing buffer begin/end

  • ↑↓ indicate that there is more text above/below the screen
  • ｢｣ indicate begin/end of the buffer text within displayed part of the buffer
  • These can be enabled using ~(setq-default indicate-buffer-boundaries 'left)~

• Using ~helm-org-ql~ for searching across knowledge base, git commits, and emails

  • I modify the default ~org-ql~ search adding a number of shortcuts to quickly filter by tag/todo keyword
    • https://github.com/yantar92/emacs-config/blob/master/config.org#trying-org-ql
      • My modifications are tailored to my own fork of org-ql: https://github.com/yantar92/org-ql
      • Although the particular special feature I used here (custom default org-ql predicate) is already implemented upstream, though using different defcustom.
    • I have a custom helm search, unifying org-ql, notmuch search (for emails), and git commit search
      • https://github.com/yantar92/emacs-config/blob/master/config.org#helm-org-ql
      • I also add custom helm actions to insert bookmark/commit/email Urls or Org links right from helm search.