all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kepa <gnu.cognition199@slmails.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: RE: Issue opening files with accented words, using org-attach-open
Date: Tue, 6 Aug 2024 19:37:28 +0000	[thread overview]
Message-ID: <172297305205.8.8141460233095395769.399116258@slmails.com> (raw)
In-Reply-To: <87o765k1l7.fsf@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 9008 bytes --]

Hi, Ihor



I get not output with w32-shell-execute, but... if I make a link to the file, and I try to open it, I get a backtrace (so it would be not a problem from org-attach, but from org-mode):





Debugger entered--entering a function:

* org-open-file("p:/170 Buzón/oq.pdf" nil)

  apply(org-open-file "p:/170 Buzón/oq.pdf" nil nil)

  org-link-open-as-file("p:/170 Buzón/oq.pdf" nil)





  org-link-open((link (:standard-properties [214050 nil nil nil 214078 0 nil nil nil nil nil nil nil nil #<buffer 1-TAREAS.org> nil nil (paragraph (:standard-properties [214050 214050 214050 214079 214079 0 nil nil element t (20 . 214083) nil nil nil #<buffer 1-TAREAS.org> nil nil (section ...)]))] :type "file" :type-explicit-p t :path "p:/170 Buzón/oq.pdf" :format bracket :raw-link "file:p:/170 Buzón/oq.pdf" :application nil :search-option nil)) nil)





  #f(compiled-function (&optional arg) "Open thing at point.\nThe thing can be a link, citation, timestamp, footnote, src-block or\ntags.\n\nWhen point is on a link, follow it.  Normally, files will be opened by\nan appropriate application (see `org-file-apps').  If the optional prefix\nargument ARG is non-nil, Emacs will visit the file.  With a double\nprefix argument, try to open outside of Emacs, in the application the\nsystem uses for this file type.\n\nWhen point is on a timestamp, open the agenda at the day\nspecified.\n\nWhen point is a footnote definition, move to the first reference\nfound.  If it is on a reference, move to the associated\ndefinition.\n\nWhen point is on a src-block of inline src-block, open its result.\n\nWhen point is on a citation, follow it.\n\nWhen point is on a headline, display a list of every link in the\nentry, so it is possible to pick one, or all, of them.  If point\nis on a tag, call `org-tags-view' instead.\n\nOn top of syntactically correct links, this function also tries\nto open links and timestamps in comments, node properties, and\nkeywords if point is on something looking like a timestamp or\na link." (interactive "P") #<bytecode -0x1c87900cd089f1b9>)(nil)





  apply(#f(compiled-function (&optional arg) "Open thing at point.\nThe thing can be a link, citation, timestamp, footnote, src-block or\ntags.\n\nWhen point is on a link, follow it.  Normally, files will be opened by\nan appropriate application (see `org-file-apps').  If the optional prefix\nargument ARG is non-nil, Emacs will visit the file.  With a double\nprefix argument, try to open outside of Emacs, in the application the\nsystem uses for this file type.\n\nWhen point is on a timestamp, open the agenda at the day\nspecified.\n\nWhen point is a footnote definition, move to the first reference\nfound.  If it is on a reference, move to the associated\ndefinition.\n\nWhen point is on a src-block of inline src-block, open its result.\n\nWhen point is on a citation, follow it.\n\nWhen point is on a headline, display a list of every link in the\nentry, so it is possible to pick one, or all, of them.  If point\nis on a tag, call `org-tags-view' instead.\n\nOn top of syntactically correct links, this function also tries\nto open links and timestamps in comments, node properties, and\nkeywords if point is on something looking like a timestamp or\na link." (interactive "P") #<bytecode -0x1c87900cd089f1b9>) nil)





  org--mouse-open-at-point(#f(compiled-function (&optional arg) "Open thing at point.\nThe thing can be a link, citation, timestamp, footnote, src-block or\ntags.\n\nWhen point is on a link, follow it.  Normally, files will be opened by\nan appropriate application (see `org-file-apps').  If the optional prefix\nargument ARG is non-nil, Emacs will visit the file.  With a double\nprefix argument, try to open outside of Emacs, in the application the\nsystem uses for this file type.\n\nWhen point is on a timestamp, open the agenda at the day\nspecified.\n\nWhen point is a footnote definition, move to the first reference\nfound.  If it is on a reference, move to the associated\ndefinition.\n\nWhen point is on a src-block of inline src-block, open its result.\n\nWhen point is on a citation, follow it.\n\nWhen point is on a headline, display a list of every link in the\nentry, so it is possible to pick one, or all, of them.  If point\nis on a tag, call `org-tags-view' instead.\n\nOn top of syntactically correct links, this function also tries\nto open links and timestamps in comments, node properties, and\nkeywords if point is on something looking like a timestamp or\na link." (interactive "P") #<bytecode -0x1c87900cd089f1b9>) nil)





  apply(org--mouse-open-at-point #f(compiled-function (&optional arg) "Open thing at point.\nThe thing can be a link, citation, timestamp, footnote, src-block or\ntags.\n\nWhen point is on a link, follow it.  Normally, files will be opened by\nan appropriate application (see `org-file-apps').  If the optional prefix\nargument ARG is non-nil, Emacs will visit the file.  With a double\nprefix argument, try to open outside of Emacs, in the application the\nsystem uses for this file type.\n\nWhen point is on a timestamp, open the agenda at the day\nspecified.\n\nWhen point is a footnote definition, move to the first reference\nfound.  If it is on a reference, move to the associated\ndefinition.\n\nWhen point is on a src-block of inline src-block, open its result.\n\nWhen point is on a citation, follow it.\n\nWhen point is on a headline, display a list of every link in the\nentry, so it is possible to pick one, or all, of them.  If point\nis on a tag, call `org-tags-view' instead.\n\nOn top of syntactically correct links, this function also tries\nto open links and timestamps in comments, node properties, and\nkeywords if point is on something looking like a timestamp or\na link." (interactive "P") #<bytecode -0x1c87900cd089f1b9>) nil)

  org-open-at-point(nil)

  funcall-interactively(org-open-at-point nil)

  call-interactively(org-open-at-point)





  #f(compiled-function (&optional indent arg interactive) "Goto next table row or insert a newline.\n\nCalls `org-table-next-row' or `newline', depending on context.\n\nWhen optional INDENT argument is non-nil, call\n`newline-and-indent' with ARG, otherwise call `newline' with ARG\nand INTERACTIVE.\n\nWhen `org-return-follows-link' is non-nil and point is on\na timestamp, a link or a citation, call `org-open-at-point'.\nHowever, it will not happen if point is in a table or on a \"dead\"\nobject (e.g., within a comment).  In these case, you need to use\n`org-open-at-point' directly." (interactive "i\nP\np") #<bytecode 0x12021b210b6f462a>)(nil nil 1)





  apply(#f(compiled-function (&optional indent arg interactive) "Goto next table row or insert a newline.\n\nCalls `org-table-next-row' or `newline', depending on context.\n\nWhen optional INDENT argument is non-nil, call\n`newline-and-indent' with ARG, otherwise call `newline' with ARG\nand INTERACTIVE.\n\nWhen `org-return-follows-link' is non-nil and point is on\na timestamp, a link or a citation, call `org-open-at-point'.\nHowever, it will not happen if point is in a table or on a \"dead\"\nobject (e.g., within a comment).  In these case, you need to use\n`org-open-at-point' directly." (interactive "i\nP\np") #<bytecode 0x12021b210b6f462a>) (nil nil 1))

  org-return(nil nil 1)

  funcall-interactively(org-return nil nil 1)





  command-execute(org-return)



[cid:image001.png@01DAE848.A4D542E0]



https://i.ibb.co/NynYwVB/Captura-de-pantalla-2024-08-06-213339.png



Best regards



-----Original Message-----
From: yantar92 at posteo.net <yantar92_at_posteo_net_bkabf@simplelogin.co>
Sent: Tuesday, August 6, 2024 7:23 PM
To: Kepa <gnu.cognition199@slmails.com>
Cc: emacs-orgmode at gnu.org <emacs-orgmode_at_gnu_org_kqcgkjat@simplelogin.co>
Subject: RE: Issue opening files with accented words, using org-attach-open



Kepa <gnu.cognition199@slmails.com<mailto:gnu.cognition199@slmails.com>> writes:



> I get no error using " M-x debug-on-entry <RET> org-open-file ".

>

> If I use org-attach-open from the attach menu, I get this backtrace:

>

> Debugger entered--entering a function:

> * org-open-file("p:/170 Buzón/oq.pdf" nil)

>   org-attach-open(nil)

>   funcall-interactively(org-attach-open nil)

>   command-execute(org-attach-open)

>   org-attach()

>   funcall-interactively(org-attach)

>   command-execute(org-attach)

>

>

> Although I've now noticed that the error only occurs when the file is on the local network. If it's on my hard drive, access works correctly. P: is a local network drive.



Ok.

What about the same steps, but using

M-x debug-on-entry... w32-shell-execute ?



--

Ihor Radchenko // yantar92,

Org mode contributor,

Learn more about Org mode at <https://orgmode.org/>.

Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>



[-- Attachment #1.2: Type: text/html, Size: 15216 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 20108 bytes --]

  reply	other threads:[~2024-08-06 19:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-04 20:37 Issue opening files with accented words, using org-attach-open Kepa
2024-08-05  4:33 ` tomas
2024-08-05  9:04   ` Kepa
2024-08-05  9:28     ` tomas
2024-08-05 18:53 ` Ihor Radchenko
2024-08-05 20:24   ` Kepa
2024-08-05 20:44     ` Kepa
2024-08-06  4:28       ` tomas
2024-08-06 17:23     ` Ihor Radchenko
2024-08-06 19:37       ` Kepa [this message]
2024-08-10 13:53         ` Ihor Radchenko
2024-08-10 17:51           ` Kepa
2024-08-11 16:31             ` Ihor Radchenko

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=172297305205.8.8141460233095395769.399116258@slmails.com \
    --to=gnu.cognition199@slmails.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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.