all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Fernando de Morais <fernandodemorais.jf@gmail.com>
To: 62444@debbugs.gnu.org
Cc: emacs-erc@gnu.org, daniel@dpettersson.net, jp@neverwas.me
Subject: bug#62444: [PATCH] erc: Fix "dcc get" flag parsing
Date: Sat, 08 Jul 2023 00:22:54 -0300	[thread overview]
Message-ID: <87zg47w0hd.fsf__4204.75529260642$1688786661$gmane$org@sekai.mail-host-address-is-not-set> (raw)
In-Reply-To: <87mt3i56l8.fsf__17405.3245967784$1680994480$gmane$org@neverwas.me> (J. P.'s message of "Sat, 08 Apr 2023 15:53:23 -0700")

Hello J.P. and Daniel,

I don't know if this behaviour is related to the changes discussed in
this bug report, but I can no longer receive files from senders whose
nicknames contains a "|" pipe character.

Example:

	/DCC GET EXAMPLE|Nick file_name.txt

ERC returns in its buffer (followed by an *Apropos* buffer showing up in
another window):

	*** DCC: Nick undefined subcommand. GET, CHAT and LIST are defined.

Thanks in advance for any help.

-- 
Regards,
Fernando de Morais.





  reply	other threads:[~2023-07-08  3:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25 15:25 bug#62444: [PATCH] erc: Fix "dcc get" flag parsing Daniel Pettersson
2023-03-26  4:10 ` J.P.
     [not found] ` <87a600xidp.fsf@neverwas.me>
2023-03-27  3:50   ` J.P.
2023-04-05 18:27 ` Daniel Pettersson
2023-04-08 22:53   ` J.P.
2023-07-08  3:22     ` Fernando de Morais [this message]
     [not found]     ` <878rbrxfkl.fsf@gmail.com>
2023-07-08  4:24       ` J.P.
2023-07-08 12:56         ` Fernando de Morais
     [not found]         ` <87sf9ywohp.fsf@gmail.com>
2023-07-08 14:18           ` J.P.
     [not found]           ` <87ttue32rd.fsf@neverwas.me>
2023-07-09 18:02             ` Fernando de Morais
     [not found]             ` <871qhh55g2.fsf@gmail.com>
2023-07-14  2:22               ` J.P.

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='87zg47w0hd.fsf__4204.75529260642$1688786661$gmane$org@sekai.mail-host-address-is-not-set' \
    --to=fernandodemorais.jf@gmail.com \
    --cc=62444@debbugs.gnu.org \
    --cc=daniel@dpettersson.net \
    --cc=emacs-erc@gnu.org \
    --cc=jp@neverwas.me \
    /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.