all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Ergus <spacibba@aol.com>,
	34798@debbugs.gnu.org, Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#34798: 27.0.50; xclip issue in tramp mode
Date: Mon, 15 Apr 2019 21:17:04 -0400	[thread overview]
Message-ID: <878swazr3j.fsf@gmail.com> (raw)
In-Reply-To: <8736nrkzkb.fsf@gmx.de> (Michael Albinus's message of "Wed, 13 Mar 2019 08:23:32 +0100")

tags 34798 fixed
close 34798 
quit

Michael Albinus <michael.albinus@gmx.de> writes:

> Ergus <spacibba@aol.com> writes:

>> On the other hand it looks like there is a bug or undocumented/unclear
>> feature in the process-file function.
>>
>> A special comment should be added in all the external process call
>> functions to clarify whats the expected behaviour in tramp mode.

> I'm sorry, reading this bug thread I fail to see what's missing in the
> process-file documentation. Could you pls explain?

Not sure what Ergus is getting at either, but since the original bug
seems to be fixed I'm closing it, and perhaps unclear doc of
process-file can be followed up in Bug#20737.





  reply	other threads:[~2019-04-16  1:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-09 23:11 bug#34798: 27.0.50; xclip issue in tramp mode Ergus
2019-03-11 20:16 ` Stefan Monnier
2019-03-12 22:44   ` Ergus
2019-03-13  7:23     ` Michael Albinus
2019-04-16  1:17       ` Noam Postavsky [this message]
2019-04-16  7:10         ` Michael Albinus
     [not found] ` <handler.34798.C.1555377435564.notifdonectrl.0@debbugs.gnu.org>
2019-04-16 14:16   ` bug#34798: acknowledged by developer (Re: bug#34798: 27.0.50; xclip issue in tramp mode) Ergus
2019-04-16 14:34     ` Robert Pluim
2019-04-16 16:00       ` Eli Zaretskii
2019-04-16 16:55         ` Alex Gramiak
2019-04-16 15:05     ` Eli Zaretskii

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=878swazr3j.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=34798@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=spacibba@aol.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 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.