unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eshel Yaron <me@eshelyaron.com>
To: Joseph Turner <joseph@breatheoutbreathe.in>
Cc: Emacs Devel Mailing List <emacs-devel@gnu.org>,
	 Adam Porter <adam@alphapapa.net>
Subject: Re: How to autoload easy-menu?
Date: Sat, 14 Oct 2023 12:33:56 +0200	[thread overview]
Message-ID: <m1a5slqyqz.fsf@eshelyaron.com> (raw)
In-Reply-To: <87a5slg6dc.fsf@breatheoutbreathe.in> (Joseph Turner's message of "Fri, 13 Oct 2023 21:35:55 -0700")

Joseph Turner <joseph@breatheoutbreathe.in> writes:

> Thank you for testing out hyperdrive.el!!!  Now, the "Tools > Hyperdrive"
> menu is added only after the user calls `hyperdrive-menu-bar-mode':
>
> https://git.sr.ht/~ushin/hyperdrive.el/commit/0869edbd
>

Nice :)

FYI when trying this on macOS I had some issues with the `hyper-gateway`
program, it basically fails and quits after most hyperdrive.el commands.
For example, when I call `hyperdrive-hyper-gateway-version` it prints:

--8<---------------cut here---------------start------------->8---
Request: {
  method: 'GET',
  url: '/',
  headers: {
    host: 'localhost:4973',
    'user-agent': 'curl/8.1.2',
    accept: '*/*',
    'accept-encoding': 'deflate, gzip'
  }
}
Requested: {
  method: 'GET',
  url: 'hyper://',
  status: 500,
  responseHeaders: { 'content-type': 'text/plain; charset=utf-8' }
}
Error [ERR_HTTP_HEADERS_SENT]: Cannot write headers after they are sent to the client
    at new NodeError (node:internal/errors:406:5)
    at ServerResponse.writeHead (node:_http_server:345:11)
    at Server.<anonymous> (file:///usr/local/lib/node_modules/hyper-gateway/src/index.js:131:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'ERR_HTTP_HEADERS_SENT'
}
node:internal/errors:497
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_HTTP_HEADERS_SENT]: Cannot write headers after they are sent to the client
    at new NodeError (node:internal/errors:406:5)
    at ServerResponse.writeHead (node:_http_server:345:11)
    at Server.<anonymous> (file:///usr/local/lib/node_modules/hyper-gateway/src/index.js:139:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'ERR_HTTP_HEADERS_SENT'
}
--8<---------------cut here---------------end--------------->8---


> We may consider adding a defcustom to make `hyperdrive-menu-bar-mode'
> add "Hyperdrive" menu to the global map instead of a submenu. WDYT?

I don't really have a strong opinion about this one.


Cheers,

Eshel



  reply	other threads:[~2023-10-14 10:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  0:07 How to autoload easy-menu? Joseph Turner
2023-10-12 21:17 ` Joseph Turner
2023-10-13  7:13   ` Eshel Yaron
2023-10-14  4:35     ` Joseph Turner
2023-10-14 10:33       ` Eshel Yaron [this message]
2023-10-15  1:35         ` Joseph Turner

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=m1a5slqyqz.fsf@eshelyaron.com \
    --to=me@eshelyaron.com \
    --cc=adam@alphapapa.net \
    --cc=emacs-devel@gnu.org \
    --cc=joseph@breatheoutbreathe.in \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).