From: Eric Hanchrow <eric.hanchrow@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 32418@debbugs.gnu.org
Subject: bug#32418: 26.1; M-C-q with lsp-python leaves point at beginning of buffer
Date: Fri, 10 Aug 2018 15:55:01 -0700 [thread overview]
Message-ID: <CAHZoxq-=LZ-U-ETzbjKxNnFDab+eLRYFat3BNK7pOWqsw5csgg@mail.gmail.com> (raw)
In-Reply-To: <40o9e96dg7.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
Yes, I suppose so; I hadn't even thought about it.
On Fri, Aug 10, 2018 at 3:53 PM Glenn Morris <rgm@gnu.org> wrote:
>
> Isn't this an issue for whoever maintains lsp-python?
>
[-- Attachment #2: Type: text/html, Size: 425 bytes --]
prev parent reply other threads:[~2018-08-10 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 21:09 bug#32418: 26.1; M-C-q with lsp-python leaves point at beginning of buffer Eric Hanchrow
2018-08-10 22:53 ` Glenn Morris
2018-08-10 22:55 ` Eric Hanchrow [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
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='CAHZoxq-=LZ-U-ETzbjKxNnFDab+eLRYFat3BNK7pOWqsw5csgg@mail.gmail.com' \
--to=eric.hanchrow@gmail.com \
--cc=32418@debbugs.gnu.org \
--cc=rgm@gnu.org \
/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).