all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, Juri Linkov <juri@linkov.net>,
	"Charles A. Roelli" <charles@aurox.ch>
Cc: 32990@debbugs.gnu.org
Subject: bug#32990: 26.1.50; isearch-forward + t-m-m/mark-active doc
Date: Sat, 17 Nov 2018 10:29:32 +0100	[thread overview]
Message-ID: <5BEFDF7C.7040301@gmx.at> (raw)
In-Reply-To: <f43b8c6e-b9e1-4ef9-9bca-bc2f4c4f8378@default>

 > Sorry for jumping in here in ignorance, but when
 > I follow the recipe for bug #8213 with Emacs 26
 > I can move the window divider with no problem.

Thanks for checking.  Apparently that bug was fixed in some version of
Emacs 24 and is hopefully marked as done now.

 > That does exit Isearch, but that doesn't seem to
 > be what the bug report was about - it says that
 > you cannot move the divider.

Right.  It would be nice to be able to resize windows during Isearch
without causing the latter to exit.  That would, however, amount to a
feature request and the bug report did not ask for it.

 > I'm on Windows 10, though, not Windows 7 as in
 > the bug report.  And maybe I'm missing something.

Hopefully not.

Thanks again, martin





  reply	other threads:[~2018-11-17  9:29 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 17:58 bug#32990: 26.1.50; isearch-forward + t-m-m/mark-active doc Charles A. Roelli
2018-10-08 20:07 ` Eli Zaretskii
2018-10-09 18:14   ` Charles A. Roelli
2018-10-09 18:21     ` Eli Zaretskii
2018-10-14 19:53       ` Charles A. Roelli
2018-10-15 15:02         ` Eli Zaretskii
2018-10-16 18:57           ` Charles A. Roelli
2018-10-20  9:59             ` Eli Zaretskii
2018-10-25 19:11               ` Charles A. Roelli
2018-10-28 10:06                 ` Charles A. Roelli
2018-10-28 15:53                   ` Eli Zaretskii
2018-10-28 17:09                     ` Charles A. Roelli
2018-11-10 13:57                       ` Charles A. Roelli
2018-11-10 14:05                         ` Eli Zaretskii
2018-11-15 19:57                           ` Charles A. Roelli
2018-11-15 20:07                             ` Eli Zaretskii
2018-11-15 22:15                             ` Juri Linkov
2018-11-16  8:53                               ` martin rudalics
2018-11-16 16:00                                 ` Drew Adams
2018-11-17  9:29                                   ` martin rudalics [this message]
2018-11-17 21:32                                     ` Juri Linkov
2018-11-18  9:22                                       ` martin rudalics
2018-11-16 20:22                               ` Charles A. Roelli
2018-11-17 21:01                                 ` Juri Linkov
2018-11-17 21:07                             ` Juri Linkov
2018-11-18  1:49                               ` Drew Adams
2018-11-18 20:24                               ` Charles A. Roelli
2018-11-18 22:42                                 ` Juri Linkov
2018-11-19 20:14                                 ` Charles A. Roelli
2018-11-19 21:44                                   ` Juri Linkov
2018-11-20 19:49                                     ` Charles A. Roelli
2018-11-21 20:14                                       ` Charles A. Roelli
2018-11-21 22:31                                         ` Juri Linkov
2018-11-22 20:29                                           ` Charles A. Roelli
2018-11-22 21:59                                             ` Juri Linkov
2018-11-23  8:17                                               ` Eli Zaretskii
2018-11-24 11:25                                                 ` Charles A. Roelli
2018-11-24 11:44                                                   ` Eli Zaretskii
2018-11-24 12:51                                                     ` Charles A. Roelli
2019-04-02  0:22                                                       ` Noam Postavsky
2018-11-10 20:34                         ` Juri Linkov

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=5BEFDF7C.7040301@gmx.at \
    --to=rudalics@gmx.at \
    --cc=32990@debbugs.gnu.org \
    --cc=charles@aurox.ch \
    --cc=drew.adams@oracle.com \
    --cc=juri@linkov.net \
    /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.