Emacs Lisp good first issues

The user is reporting that time tracking is not working specifically for ORG-Mode in GNU Emacs 26.1, while it functions correctly for other modes like Assembler, C, and makefile-gmake. They are seeking assistance or ideas to resolve this issue.

This issue describes a bug where the cursor gets stuck when moving word-by-word in Emacs when both `superword-mode` and `clojure-mode` are active. This interaction problem appears to be specific to these two modes and might require debugging their respective word-boundary definitions.

This issue reports that enabling the Lsp layer in Spacemacs interferes with the default keybindings in latex mode. Specifically, some expected keybindings, like `SPC m b`, are no longer available when both Lsp and latex layers are active. The problem is resolved by disabling the Lsp layer.

This enhancement request proposes to intelligently skip over terms within non-prose ranges, such as code blocks or comments, when performing language checks. The goal is to avoid unnecessary corrections in areas where standard prose rules may not apply, improving the accuracy and relevance of the language checking tool.

The user is inquiring about Wayland support for the project, noting that current dependencies like xclip, xdotool, xprop, and xwininfo are X11-specific. They point out a Wayland alternative for xclip (wl-clipboard) and ask about the project's plans for Wayland compatibility.

This issue proposes adding `source` aliases in Eask for the new MELPA Snapshots and MELPA Releases channels. This would provide a more convenient way for users to specify these channels when configuring their Emacs environments.

The org-ql package is crashing on macOS with a lexical-binding error when attempting to perform string queries. This prevents string-based searches from working, although the S-expression API for org-ql is functional. The issue appears to be related to how the PEG parser handles lexical binding.

When clicking a `mu4e` link within an Org mode entry, the email opens in the current window instead of the designated `*mu4e*` workspace. This behavior also causes the `*mu4e*` workspace to disappear after exiting the email, contrary to the expected behavior where the workspace should be preserved.

The user is reporting a visual misalignment issue when navigating text containing 2-wide ligatures (like 'return' or 'yield') in their editor. When the cursor is positioned after such a ligature and the user moves up or down a line, the cursor appears one visual character to the left of its expected position. This behavior is inconsistent with 1-wide ligatures, which maintain alignment.

The user wants to re-enable the ability to add words to a personal dictionary directly from the Ivy spelling interface. The current implementation of `+spell/correct` only offers default Ivy actions, and the user's attempt to customize actions for `+spell-correct-ivy-fn` resulted in unintended word deletion upon adding to the dictionary.

The user wants to achieve a horizontal split for a vterm pop-up window, similar to how eshell behaves. Currently, when trying to split a vterm pop-up window horizontally, the parent magit-status window is split instead. This suggests a potential issue with how vterm interacts with window splitting commands in this specific context.

This issue discusses potential improvements and customizations for the newly added official Coq layer in Spacemacs. The author, a user of a previous Coq layer, raises several points regarding default settings, keybindings, and documentation, seeking community feedback to ensure the official layer meets user expectations.

The user wants to customize which events update the "latest timestamp" displayed for a room. Currently, any event, including non-message changes like username updates, triggers this timestamp. This makes it difficult to quickly identify truly new messages, and the user suggests a way to filter events that affect this timestamp.

This issue proposes integrating Emacspeak, a speech system for visually impaired users, into the Doom Emacs distribution. The goal is to provide a more accessible and user-friendly Emacs experience for these users, as current setup can be complex. The proposer intends to test compatibility and contribute findings.