From: "Samuel Banya" <sbanya@fastmail.com>
To: "Robert Pluim" <rpluim@gmail.com>
Cc: "Emanuel Berg" <help-gnu-emacs@gnu.org>
Subject: Re: Emacs help from terminal
Date: Wed, 15 Jun 2022 11:52:52 -0400 [thread overview]
Message-ID: <20d7b4a5-7ef7-497c-8d35-b40689026517@www.fastmail.com> (raw)
In-Reply-To: <871qvqypvy.fsf@gmail.com>
Yeah I usually use 'vterm' since even though a lot of people praise 'eshell' for running commands, a lot of the output that is received comes out jenky, and this isn't necessarily for ncurses stuff, but for normal commands.
I've tried to incorporate popper into my workflow which works fine on Linux (Manjaro) with (M-`) for the keybinding, but on MacOS, it never comes up.
I still have no idea why I can't combine M-` on MacOS in Emacs. I've tried using 'C-h k' but no response with that combo.
Still a mystery to me.
On Wed, Jun 15, 2022, at 10:15 AM, Robert Pluim wrote:
> >>>>> On Wed, 15 Jun 2022 10:06:23 -0400, "Samuel Banya" <sbanya@fastmail.com> said:
>
> Samuel> Wow, that's awesome, I never knew this about 'C-z' and 'fg' keybinding
> Samuel> commands to be able to suspend Emacs.
>
> Samuel> That's super cool, thanks for this, putting this in my notes as I
> Samuel> usually use GUI Emacs but this would be cool on headless terminal
> Samuel> boxes.
>
> Just wait until you realize you can run a shell inside emacs, so you
> never need to suspend it :-)
>
> Robert
> --
>
next prev parent reply other threads:[~2022-06-15 15:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 22:43 Emacs help from terminal carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-14 4:51 ` tomas
2022-06-14 10:11 ` Emanuel Berg
2022-06-14 13:38 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-14 13:56 ` Samuel Banya
2022-06-14 14:03 ` Emanuel Berg
2022-06-14 13:57 ` tomas
2022-06-14 14:05 ` Emanuel Berg
2022-06-14 14:00 ` Emanuel Berg
2022-06-14 14:13 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-14 14:37 ` Michael Heerdegen
2022-06-14 21:52 ` Jean Louis
2022-06-14 22:47 ` Emanuel Berg
2022-06-15 5:29 ` Jean Louis
2022-06-15 8:52 ` Emanuel Berg
2022-06-15 17:00 ` Tomas Hlavaty
2022-06-15 17:16 ` Emanuel Berg
2022-06-15 19:55 ` Emanuel Berg
2022-06-15 23:40 ` Tomas Hlavaty
2022-06-15 23:52 ` Emanuel Berg
2022-06-16 5:52 ` Tomas Hlavaty
2022-06-16 7:12 ` Emanuel Berg
2022-06-15 10:22 ` Michael Heerdegen
2022-06-15 10:26 ` Emanuel Berg
2022-06-15 14:06 ` Samuel Banya
2022-06-15 14:15 ` Robert Pluim
2022-06-15 15:16 ` Emanuel Berg
2022-06-15 15:52 ` Samuel Banya [this message]
2022-06-15 15:59 ` Emanuel Berg
2022-06-16 7:48 ` Robert Pluim
2022-06-16 14:45 ` Samuel Banya
2022-06-16 5:34 ` Jean Louis
2022-06-16 7:09 ` Emanuel Berg
2022-06-16 15:08 ` Jean Louis
2022-06-16 17:31 ` Emanuel Berg
2022-06-16 17:36 ` Jean Louis
2022-06-17 18:36 ` Emanuel Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20d7b4a5-7ef7-497c-8d35-b40689026517@www.fastmail.com \
--to=sbanya@fastmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rpluim@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).