Open source and released on both ios and android!!

I'm interested in getting emacs to work on my tablet (Samsung A9+, if it mattters). Previously I had them installed separately, which kinda worked (ish) with the unfortunate limitation of the two environments not being able to really talk to one another, and specifically emacs not being able to access some of the tooling available on the termux side of things. So, I uninstalled both, and started over.

Based on what I had read online, it appears that I need to install termux first, then emacs - but via apk from the termux/source-forge repo - then do a little config, and then the two should be able to play nice together.

The first problem/concern was that the versions of Emacs in that termux repo don't seem to correspond to normal releases of mainstream emacs i.e. the version of v31 is at something like .0.50, vs 31.1.x, and AFAIK there isn't a main stream release of Emacs 32 yet. Kinda confusing, to say the least. I saw at least one reference to installing termux from f-droid, and another saying instead to install it via apk downloaded from that same repo. IIRC, the first way worked, and the second did not. I tried installing emacs for android (via apk) from the gnu.org repo, in their /termux directory, and when that didn't appear to work, tried installing it from the termux/source-forge repo. Which now fails saying that it conflicts with some other existing package.

At this point... what's my best path forward? How do I nuke/reset things as far as emacs and termux are concerned, and start over? Which version of termux do I need to install, and from where? Which version of emacs?

Thanks!

For those who like to use org-agenda, how do you take it with you when you're not at your computer?

I'd like to use org-agenda for planning work tasks and noting errands. I don't work in an environment where I can just open up my laptop and this wouldn't be practical in town, so I'm restricted to my phone

Edit: Forgot to mention I'm on Android

This is a book I found when I was just starting to use Emacs a couple of years ago, and I got a huge amount from it. But every time I see a list of suggested resources for beginners (and others), I never see it mentioned, and it baffles me. I've been meaning to give it a plug for a long time and noticed it was updated fairly recently, so thought this would be a good time.

Don't be put off by the fact that it's a "work in progress" -- the pdf is 641 pages and it's more than enough to get you proficient; the areas the book doesn't yet cover are generally pretty advanced or specialized. As a tutorial it's exemplary: clear, detailed, accurate, well-written. The pdf (which I read in Emacs, conveniently) is beautifully laid out.

I highly, highly recommend it.

This is a thread for smaller, miscellaneous items that might not warrant a full post on their own.

The default sort is new to ensure that new items get attention.

If something gets upvoted and discussed a lot, consider following up with a post!

Search for previous "Tips, Tricks" Threads.

Fortnightly means once every two weeks. We will continue to monitor the mass of confusion resulting from dark corners of English.

https://i.redd.it/lacddemakyth1.gif

Hi r/emacs and r/orgmode,

If you rely on Org-mode for time tracking and scheduling, you’ve probably hit this dilemma when tackling a large task:

1. Headlines (** TODO) are too heavy: If you break down every micro-step of a 2-hour task into subheadings, your agenda gets flooded, your outline gets cluttered, and scheduling becomes noisy.
2. Checklists (- [ ]) lack time tracking and budgeting: Checklists are lightweight and ideal for micro-steps, but in vanilla Org they are second-class citizens. They don't support individual effort estimates, micro-timers, or roll-up budgeting.
3. Scope creep is invisible: You start working on a 2-hour task, add subtasks on the fly, and only realize you planned 3.5 hours of work after your schedule has drifted.

To solve this, used AI to build org-focus-hud — a distraction-free, monotasking execution cockpit that bridges the gap between high-level TODO headlines and granular checklist items.

⚡ Key Features

1. Checklist Time Tracking & Micro-Timers

• Checklist Estimates: Add time estimates directly to items (- [ ] Validate token [25m], [1.5h], [90m]). The HUD renders clean right-aligned effort badges ([0:25], [✓ 0:30]).
• Active Focus (f or RET): Press f on any checklist item to set it in-progress (▶ [-]). It automatically clocks into the parent task and starts a live micro-timer (e.g. ⏱️ 14m / 25m) synchronized with org-clock.
• Lockstep Pausing (p): Press p to pause both the main task clock and checklist micro-timer (⏱️ 14m / 25m (paused)). Resuming seamlessly continues elapsed time accumulation.

2. Dynamic Scope Budgeting & Deficit Warnings

• Scope Allocation Bar: Visual ledger tracking Done, Left, and Reserve against the parent task's :EFFORT: envelope: ALLOC: [█████░░░░░░░░░░·····] 30m Done · 1h Left · 30m Reserve / 2h
• Real-time Deficit Alert: If you decompose a task on the fly (k) and subtasks exceed the parent effort, the HUD immediately warns of scope creep: ALLOC: [████████░░░░░░░░░░▓▓] 2h 15m planned · ⚠️ +15m deficit / 2h
• Nested Envelopes & Rollups: Multi-level checklists roll up child efforts leaf-first ([Σ 1:15], [1:15 / 1:30]) without double-counting.

3. Zero-Context-Switching Workflow

• Automatic Milestone Capture: Marking an item complete ([X]) automatically clocks a timestamped milestone entry into your :LOGBOOK: drawer with the exact duration spent.
• In-Cockpit Manipulation: Add items (k), edit text & estimates simultaneously (e), reorder items across body text (M-j / M-k), or indent/outdent (M-h / M-l) without leaving the HUD.
• Quick Capture: Append work log entries (l), capture quick notes (n), add child subtasks (s), or queue sibling tasks (a).
• Vanilla Compatible: Works out of the box with standard org-clock, :EFFORT:, and :LOGBOOK:. Seamlessly integrates with org-auto-scheduler if installed.

📦 Installation & Links

• GitHub Repository: https://github.com/SSD2019/org-focus-hud
• Available via use-package with straight.el, quelpa, or manual load.

Feedback, feature requests, and workflow questions are welcome!

https://sachachua.com/blog/2026/10/emacs-lisp-parse-page-ranges-insert-issue-references/ mentions a way to expand string ranges into e.g. #47, #48, #49, #50, #51, #52, #53, #54 and comes up with a function for that.

But there is already a library that does this and more: https://github.com/abo-abo/tiny

For this exact example, you'd type m47, 54|#%d and hit C-; (if you bound that to tiny-expand) and you'd get "#47, #48, #49, #50, #51, #52, #53, #54".

The syntax is m followed by your range, and optionally a format string after a |. So if you didn't need the # before each number it becomes even simpler: m47, 54. Or you can change the separator: m1;3 becomes "1;2;3".

You can even put in lisp expressions in there and drop the parentheses, it's extremely powerful.