all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Leo Liu <sdl.web@gmail.com>
Cc: 63428-done@debbugs.gnu.org, william.emerson.tower@gmail.com
Subject: bug#63428: 29.0.60; Octave Mode: Interacting with plots
Date: Sun, 9 Jun 2024 13:59:28 -0700	[thread overview]
Message-ID: <CADwFkm=TSzSnwvWuR=0z=HStEiOpQoSm60vaikLBmkkMJEUMag@mail.gmail.com> (raw)
In-Reply-To: <CADwFkm=J2K_egReYzdD2Z_63=dZ0MbHq1pT1=48rZZnm2XUUuA@mail.gmail.com> (Stefan Kangas's message of "Fri, 22 Dec 2023 02:15:29 -0800")

Stefan Kangas <stefankangas@gmail.com> writes:

> Leo Liu <sdl.web@gmail.com> writes:
>
>> On 2023-09-06 13:27 -0700, Stefan Kangas wrote:
>>>> Failure to do so results in the user not being able to interact with
>>>> generated graphs and figures with the mouse or keyboard. Which is very
>>>> frustrating!
>>
>> I failed to understand why --no-line-editing would interfere with
>> interaction with graphs. --no-line-editing is there because line editing
>> is provided for by emacs/comint.
>>
>> Are those graphs written to disk (and shown in emacs), or displayed in a
>> (GUI) popup?
>
> I noticed that the bug reporter wasn't copied into your reply, so I did
> that here.
>
>>
>>> Leo or John, could you perhaps comment on the above? Thanks in advance.
>>
>> -- Leo

More information was requested, but none was given within 6 months, so
I'm closing this bug.  If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.





      reply	other threads:[~2024-06-09 20:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 20:56 bug#63428: 29.0.60; Octave Mode: Interacting with plots william.emerson.tower
2023-09-06 20:27 ` Stefan Kangas
2023-09-07  6:37   ` Leo Liu
2023-12-22 10:15     ` Stefan Kangas
2024-06-09 20:59       ` Stefan Kangas [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkm=TSzSnwvWuR=0z=HStEiOpQoSm60vaikLBmkkMJEUMag@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=63428-done@debbugs.gnu.org \
    --cc=sdl.web@gmail.com \
    --cc=william.emerson.tower@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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.