all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Live System User <nyc4bos@aol.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 32447@debbugs.gnu.org
Subject: bug#32447: 27.0.50; TRAMP branch: "C-x &" does not honor read-only with "C-x C-r"
Date: Thu, 16 Aug 2018 07:09:06 -0400	[thread overview]
Message-ID: <87h8jua7ql.fsf@aol.com> (raw)
In-Reply-To: <87lg96a97g.fsf@aol.com> (Live System User's message of "Thu, 16 Aug 2018 06:37:23 -0400")

Hi,

Live System User <nyc4bos@aol.com> writes:

> Michael Albinus <michael.albinus@gmx.de> writes:
>
>> Live System User <nyc4bos@aol.com> writes:
>>
>>> Hi,
>>
>> Hi,
>>
>>> 	When attempting to open files asyncronously, "C-x &"
>>> 	doesn't appear to honor read-only mode:
>>>
>>> 	      C-x & C-x C-r lisp/*.el
>>>
>>> 	The file buffers were created, however, they ere all
>>> 	writable.
>>
>> Should be fixed now. Could you, pls, check?
>
>   Yes, it is fixed.

    BTW a fix is needed for "C-x C-v" '(find-alternate-file)'

    When used with "C-x &" you get an error:

       C-x & C-x C-v lisp/*.el
       
window-normalize-buffer-to-switch-to: Wrong type argument: stringp,
(#<buffer xwidget.el> #<buffer xt-mouse.el> #<buffer xml.el> #<buffer
xdg.el> #<buffer x-dnd.el> #<buffer woman.el> #<buffer winner.el>
#<buffer window.el> #<buffer windmove.el> #<buffer widget.el> ...)

     Should I open up a new bug report for this?

     Thanks.


>
>   Thanks!
>
>>
>>> 	Thanks.
>>
>> Best regards, Michael.





  reply	other threads:[~2018-08-16 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 16:39 bug#32447: 27.0.50; TRAMP branch: "C-x &" does not honor read-only with "C-x C-r" Live System User
2018-08-15 18:20 ` Michael Albinus
2018-08-16  8:05 ` Michael Albinus
2018-08-16 10:37   ` Live System User
2018-08-16 11:09     ` Live System User [this message]
2018-08-16 12:46       ` Michael Albinus

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=87h8jua7ql.fsf@aol.com \
    --to=nyc4bos@aol.com \
    --cc=32447@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.