unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Gregory Heytings <gregory@heytings.org>
Cc: 48249@debbugs.gnu.org
Subject: bug#48249: 28.0.50; Regression: emacs confused about window configuration due to ido-mode and/or winner-mode
Date: Thu, 06 May 2021 15:22:55 +0100	[thread overview]
Message-ID: <877dkc54cg.fsf@tcd.ie> (raw)
In-Reply-To: <531453ddd635ba61499b@heytings.org> (Gregory Heytings's message of "Thu, 06 May 2021 13:38:05 +0000")

Gregory Heytings <gregory@heytings.org> writes:

>>> [For some reason my emails to Basil are rejected by Outlook ("host
>>> tcd-ie.mail.protection.outlook.com[104.47.4.36] said: 550 5.7.606 Access
>>> denied"), so I send this mail to the bugtracker instead, hoping that he'll
>>> get them.]
>>
>> FWIW, my university email is hosted by Gmail.  I'll send you the relevant
>> email headers I'm seeing off-list.
>
> Not by Gmail, by Microsoft (Outlook):

No, it's hosted by Gmail.  Clearly they also use Outlook behind the
scenes.

> $ dig +short -t mx tcd.ie
> 10 tcd-ie.mail.protection.outlook.com.
>
> Whenever you're in the recipient list I receive a "host
> tcd-ie.mail.protection.outlook.com[104.47.4.36] said: 550 5.7.606 Access denied"
> error message.  I'm the one who can do something about it, not you, but removing
> oneself from Outlook's blocklists is a painful process.

Godspeed.

>>> As I said a few hours ago: could you try to revert 7c2ebf6e23 locally and see
>>> if the issue persists?
>>
>> I can't revert the commit cleanly, but I can reproduce Dima's recipe on that
>> revision and not on its parent.
>
> Indeed, but what about your recipe (bug#48229)?

Same story, but as I said upthread that recipe is a duplicate of
bug#47766, which was fixed today.

Thanks,

-- 
Basil





  parent reply	other threads:[~2021-05-06 14:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06  3:50 bug#48249: 28.0.50; Regression: emacs confused about window configuration due to ido-mode and/or winner-mode Dima Kogan
2021-05-06  7:30 ` Gregory Heytings
2021-05-06  8:04   ` Eli Zaretskii
2021-05-06  8:17     ` Gregory Heytings
2021-05-06  9:39       ` Eli Zaretskii
2021-05-06  9:57         ` Gregory Heytings
2021-05-06 10:15           ` Eli Zaretskii
2021-05-06 11:48             ` Gregory Heytings
2021-05-06 12:30 ` Basil L. Contovounesios
2021-05-06 12:39   ` Gregory Heytings
2021-05-06 13:25     ` Basil L. Contovounesios
2021-05-06 13:38       ` Gregory Heytings
2021-05-06 13:58         ` Gregory Heytings
2021-05-06 14:22         ` Basil L. Contovounesios [this message]
2021-05-06 14:49     ` Basil L. Contovounesios
2021-05-06 19:25   ` Alan Mackenzie
2021-05-07  9:49   ` Alan Mackenzie
2021-05-07 10:24     ` Basil L. Contovounesios
2021-05-07 12:02     ` Gregory Heytings
2021-05-07 12:43       ` Alan Mackenzie
2021-05-07 20:30     ` Dima Kogan
2021-05-08 12:30       ` Alan Mackenzie

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=877dkc54cg.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=48249@debbugs.gnu.org \
    --cc=gregory@heytings.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).