unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: "Lars Ingebrigtsen" <larsi@gnus.org>,
	"Iñigo Serna" <inigoserna@gmx.com>,
	emacs-devel@gnu.org, "Eli Zaretskii" <eliz@gnu.org>
Subject: Re: PROPOSAL: New function ffap-ip-at-point
Date: Sat, 23 Jul 2022 09:39:44 +0200	[thread overview]
Message-ID: <87mtd0xoov.fsf@linux-m68k.org> (raw)
In-Reply-To: <87h7389tff.fsf@gmail.com> (Robert Pluim's message of "Sat, 23 Jul 2022 09:31:16 +0200")

On Jul 23 2022, Robert Pluim wrote:

> How far down the rabbit hole do we want to go, knowing that libc has
> already done this? Note: "0343.1.2.3" is a valid representation of an
> IPv4 address, as is "0", or "1".

Or "0xe3010203".

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."



      parent reply	other threads:[~2022-07-23  7:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22  8:49 PROPOSAL: New function ffap-ip-at-point Iñigo Serna
2022-07-22  9:36 ` Robert Pluim
2022-07-22 11:20 ` Eli Zaretskii
2022-07-22 14:46   ` Iñigo Serna
2022-07-22 15:01     ` Eli Zaretskii
2022-07-22 15:04     ` Brian Cully via Emacs development discussions.
2022-07-22 15:28       ` Iñigo Serna
2022-07-22 15:09     ` Lars Ingebrigtsen
2022-07-22 15:34       ` Iñigo Serna
2022-07-22 15:55         ` Robert Pluim
2022-07-22 20:10         ` Lars Ingebrigtsen
2022-07-23  7:31           ` Robert Pluim
2022-07-23  7:37             ` Lars Ingebrigtsen
2022-07-23  7:46               ` Robert Pluim
2022-07-23  7:47                 ` Lars Ingebrigtsen
2022-07-26 12:21                   ` Robert Pluim
2022-07-26 12:48                     ` Eli Zaretskii
2022-07-26 12:54                       ` Robert Pluim
2022-07-23  7:39             ` Andreas Schwab [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=87mtd0xoov.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=inigoserna@gmx.com \
    --cc=larsi@gnus.org \
    --cc=rpluim@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 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).