doomemacs/bin
Henrik Lissner 8d2cf32fef
feat(cli): add doom.ps1 for Windows users
c9acdb7 removes doom.cmd because it was broken in most cases. This adds
doom.ps1; an alternative script for Windows+Powershell users, which
properly initializes the state it needs. Naturally, it requires
Powershell 3+ be installed on your systems, but it can be invoked from
either cmd.exe or PowerShell.exe.

This is the first powershell script I've ever written, so I expect edge
cases (for one, shell commands passed to `exit!` will need to be guarded
against the environment).

This also requires emacs.exe be your $PATH, however, unless you set
$EMACS to its path first. E.g.

  $env:EMACS = "C:\Program Files\Emacs\emacs-29.4\bin\emacs.exe"

That said, if you use WSL2, you're still far better off using the bash
script (bin/doom).

Ref: c9acdb72a4
2024-09-07 01:05:57 -04:00
..
doom nit(cli): revise comments wrt site-run-file loading 2024-09-01 14:45:52 -04:00
doom.ps1 feat(cli): add doom.ps1 for Windows users 2024-09-07 01:05:57 -04:00
doomscript feat(cli): add doom.ps1 for Windows users 2024-09-07 01:05:57 -04:00
org-capture fix(cli): "Unknown terminal type" error on bin/org-capture 2021-11-24 22:03:21 +01:00