Re: Adding custom providers for thingatpt.el (was: [PATCH] Add support for 'thing-at-point' to get URL at point)

2024-05-18 Thread Eli Zaretskii
> Date: Tue, 30 Apr 2024 11:27:04 -0700 > Cc: e...@gnu.org, emacs-de...@gnu.org, emacs-orgmode@gnu.org > From: Jim Porter > > On 4/30/2024 4:39 AM, Ihor Radchenko wrote: > > What happens if you have multiple providers for an URL? > > You add the provider to the end, so it will have the lower

Re: [External] : Re: Adding custom providers for thingatpt.el (was: [PATCH] Add support for 'thing-at-point' to get URL at point)

2024-05-07 Thread Eli Zaretskii
> Date: Tue, 7 May 2024 09:10:59 -0700 > Cc: yanta...@posteo.net, emacs-de...@gnu.org, emacs-orgmode@gnu.org > From: Jim Porter > > On 5/7/2024 5:20 AM, Eli Zaretskii wrote: > > I disagree. These functions are nowadays the basis of many > > interactive features, and

Re: [External] : Re: Adding custom providers for thingatpt.el (was: [PATCH] Add support for 'thing-at-point' to get URL at point)

2024-05-07 Thread Eli Zaretskii
> From: Drew Adams > CC: "e...@gnu.org" , > "emacs-de...@gnu.org" > , > "emacs-orgmode@gnu.org" > Date: Tue, 7 May 2024 01:52:13 + > > I hear you. The behavior should be changed so > that, in general, bounds-of-thing-at-point etc. > return nil when there is _no thing

Re: [DISCUSSION] "quick-help" popup for org-columns (column view)

2024-04-08 Thread Eli Zaretskii
acs is full of such practices, so don't worry about that, it's quite common (and considered good practice) in Emacs Lisp. > Eli Zaretskii writes: > > In any case, we cannot change the signature of help-quick, since it's a > > public function. > > If I can't modify the funct

Re: [DISCUSSION] "quick-help" popup for org-columns (column view)

2024-04-06 Thread Eli Zaretskii
> From: Sławomir Grochowski > Cc: emacs-orgmode@gnu.org, emacs-de...@gnu.org, phil...@posteo.net, > stefankan...@gmail.com, la...@gnus.org, hmel...@gmail.com, e...@gnu.org, > i...@protesilaos.com > Date: Sat, 06 Apr 2024 22:41:32 +0200 > > But first, we need to modify `help-quick' to be more

Re: Adding custom providers for thingatpt.el (was: [PATCH] Add support for 'thing-at-point' to get URL at point)

2024-02-06 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: jporterb...@gmail.com, stefankan...@gmail.com, emacs-de...@gnu.org, > emacs-orgmode@gnu.org > Date: Tue, 06 Feb 2024 12:38:19 +0000 > > Eli Zaretskii writes: > > > I think we do want to allow extending of this, but doesn't >

Re: Adding custom providers for thingatpt.el (was: [PATCH] Add support for 'thing-at-point' to get URL at point)

2024-02-06 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: emacs-de...@gnu.org, emacs-orgmode@gnu.org > Date: Mon, 05 Feb 2024 22:56:05 + > > Jim Porter writes: > > > On 2/5/2024 7:07 AM, Ihor Radchenko wrote: > >> It would make sense to add a number of alists: > >> - bounds-of-thing-at-point-provider-alist > >> - same

Re: bug#68687: [PATCH] Use text/org media type

2024-02-01 Thread Eli Zaretskii
> From: Richard Stallman > Cc: e...@gnu.org, maniku...@gmail.com, 68...@debbugs.gnu.org, > emacs-orgmode@gnu.org, stefankan...@gmail.com > Date: Thu, 01 Feb 2024 22:40:06 -0500 > > > It may or may not depending on user customization `mm-inline-media-tests'. > > Just like with

Re: bug#68687: [PATCH] Use text/org media type

2024-01-30 Thread Eli Zaretskii
> From: Richard Stallman > Cc: maniku...@gmail.com, 68...@debbugs.gnu.org, emacs-orgmode@gnu.org, > stefankan...@gmail.com > Date: Mon, 29 Jan 2024 22:56:58 -0500 > > I am concerned that the actions described above would tend to embed > Org format and Org mode more deeply into Emacs usage.

Re: bug#68687: [PATCH] Use text/org media type

2024-01-28 Thread Eli Zaretskii
> Cc: 68...@debbugs.gnu.org, emacs-orgmode@gnu.org > Date: Sun, 28 Jan 2024 23:35:09 +0700 > From: Max Nikulin > > On 27/01/2024 10:38, Richard Stallman wrote: > > > > What is the purpose for which text/org would be used? > > In what situations would we want to send files in Org format > > and

Re: bug#68687: [PATCH] Use text/org media type

2024-01-25 Thread Eli Zaretskii
> Cc: 68...@debbugs.gnu.org, Max Nikulin , > emacs-orgmode@gnu.org > From: Ihor Radchenko > Date: Thu, 25 Jan 2024 23:43:14 + > > However, AFAIU, text/org will fall into "standards tree" in IANA media > type specification, which means that it MUST be registered, as described > in

Re: bug#68687: [PATCH] Use text/org media type

2024-01-25 Thread Eli Zaretskii
> Cc: emacs-orgmode@gnu.org > From: Stefan Kangas > Date: Thu, 25 Jan 2024 15:10:27 -0800 > > Max Nikulin writes: > > > Hi, > > > > I suggest to make the media type used for Org mode files consistent with > > the one used by XDG https://gitlab.freedesktop.org/xdg/shared-mime-info > > Currently

bug#52587: bug#59141: 28.1.90; Face :extend when all the line but trailing \n is invisible

2024-01-25 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: 59...@debbugs.gnu.org > Date: Thu, 25 Jan 2024 22:53:45 + > > Kévin Le Gouguec writes: > > >> I do not see anything wrong on the Org side. > >> Maybe Emacs should not apply :extent t attribute to the newline when the > >> text in fontified line is hidden? > > >

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2024-01-12 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: monn...@iro.umontreal.ca, emacs-orgmode@gnu.org, 65...@debbugs.gnu.org, > maniku...@gmail.com, i...@whxvd.name > Date: Fri, 12 Jan 2024 12:39:18 +0000 > > Eli Zaretskii writes: > > >> I think that I see what you m

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2024-01-12 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: monn...@iro.umontreal.ca, emacs-orgmode@gnu.org, 65...@debbugs.gnu.org, > maniku...@gmail.com, i...@whxvd.name > Date: Fri, 12 Jan 2024 12:24:01 +0000 > > Eli Zaretskii writes: > > >> Then, Org mode can instead have > >> &g

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2024-01-11 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: monn...@iro.umontreal.ca, emacs-orgmode@gnu.org, 65...@debbugs.gnu.org, > maniku...@gmail.com, i...@whxvd.name > Date: Thu, 11 Jan 2024 18:08:11 + > > Then, Org mode can instead have > > (setq-local kill-line-query-function #'org-kill-line-query) > (defun

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2024-01-11 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: monn...@iro.umontreal.ca, emacs-orgmode@gnu.org, 65...@debbugs.gnu.org, > maniku...@gmail.com, i...@whxvd.name > Date: Thu, 11 Jan 2024 16:15:13 +0000 > > Eli Zaretskii writes: > > >> So, I'd like some way to configure `kill-w

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2024-01-11 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: monn...@iro.umontreal.ca, emacs-orgmode@gnu.org, 65...@debbugs.gnu.org, > maniku...@gmail.com, i...@whxvd.name > Date: Thu, 11 Jan 2024 15:50:10 +0000 > > Eli Zaretskii writes: > > >> Then, we discussed that Emacs commands to not alwa

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2024-01-10 Thread Eli Zaretskii
> From: Stefan Monnier > Cc: Eli Zaretskii , emacs-orgmode@gnu.org, > 65...@debbugs.gnu.org, maniku...@gmail.com, i...@whxvd.name > Date: Wed, 10 Jan 2024 11:26:08 -0500 > > >> I said that remapping widely-used keys to commands that behave > >> significantly

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2024-01-10 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: monn...@iro.umontreal.ca, emacs-orgmode@gnu.org, 65...@debbugs.gnu.org, > maniku...@gmail.com, i...@whxvd.name > Date: Wed, 10 Jan 2024 13:05:19 +0000 > > Eli Zaretskii writes: > > > I said that remapping widely-used keys to commands th

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2024-01-10 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: emacs-orgmode@gnu.org, Eli Zaretskii , > 65...@debbugs.gnu.org, Max Nikulin , i...@whxvd.name > Date: Tue, 09 Jan 2024 22:33:58 + > > Stefan Monnier writes: > > >> Although, I am still interested to pursue feature request to allo

Re: [FR] Allow flattened imenu index (was: [PATCH] Add new option 'org-imenu-flatten')

2023-12-09 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: emacs-orgmode@gnu.org, 58...@debbugs.gnu.org, emacs-de...@gnu.org > Date: Sat, 09 Dec 2023 10:57:15 + > > Morgan Smith writes: > > > Ihor Radchenko writes: > > > >> Have you considered adding a "flatten" option to imenu itself? > >> That way, you could

Re: Completion of links to man pages

2023-10-05 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: maniku...@gmail.com, emacs-orgmode@gnu.org, emacs-de...@gnu.org > Date: Thu, 05 Oct 2023 16:53:57 +0000 > > Eli Zaretskii writes: > > >> > How is it different from the "M-x man" completion we already have? > >> >

Re: Completion of links to man pages

2023-10-05 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: maniku...@gmail.com, emacs-orgmode@gnu.org, emacs-de...@gnu.org > Date: Thu, 05 Oct 2023 16:05:02 +0000 > > Eli Zaretskii writes: > > >> To emacs-devel: Would it be of interest to expose man/woman completion > >> API? > >

Re: Completion of links to man pages

2023-10-05 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: emacs-orgmode@gnu.org, emacs-de...@gnu.org > Date: Thu, 05 Oct 2023 11:40:44 + > > To emacs-devel: Would it be of interest to expose man/woman completion > API? How is it different from the "M-x man" completion we already have?

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2023-09-07 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: i...@whxvd.name, 65...@debbugs.gnu.org, emacs-orgmode@gnu.org > Date: Thu, 07 Sep 2023 10:00:49 +0000 > > Eli Zaretskii writes: > > > Then perhaps just a special value for buffer-invisibility-spec, or > > some other simple variation

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2023-09-06 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: i...@whxvd.name, 65...@debbugs.gnu.org, emacs-orgmode@gnu.org > Date: Wed, 06 Sep 2023 08:30:36 +0000 > > Eli Zaretskii writes: > > >> In addition, `org-kill-line' acts specially in certain scenarios: > >> > >> For >

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2023-09-06 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: Sebastian Miele , 65...@debbugs.gnu.org, > emacs-orgmode@gnu.org > Date: Wed, 06 Sep 2023 08:23:23 +0000 > > Eli Zaretskii writes: > > >> The following would do it. I think I tested it rather thoroughly. > >> During testin

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2023-09-05 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: Max Nikulin , i...@whxvd.name, > 65...@debbugs.gnu.org, emacs-orgmode@gnu.org > Date: Tue, 05 Sep 2023 15:50:58 +0000 > > Eli Zaretskii writes: > > >> On 05/09/2023 17:29, Ihor Radchenko wrote: > >> > Confirmed. > >

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2023-09-05 Thread Eli Zaretskii
> From: Sebastian Miele > Cc: Ihor Radchenko , 65...@debbugs.gnu.org, > emacs-orgmode@gnu.org > Date: Tue, 05 Sep 2023 17:25:38 +0200 > > > From: Eli Zaretskii > > Date: Tue, 2023-09-05 14:54 +0300 > > > > […] > > > > So we could de

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2023-09-05 Thread Eli Zaretskii
> Cc: emacs-orgmode@gnu.org, 65...@debbugs.gnu.org > Date: Tue, 5 Sep 2023 21:30:58 +0700 > From: Max Nikulin > > On 05/09/2023 17:29, Ihor Radchenko wrote: > > Confirmed. > > It is a regression in comparison to e.g. org-mode-9.3.1. What changed since org-mode-9.3.1? Was it some change in

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

2023-09-05 Thread Eli Zaretskii
> Cc: 65...@debbugs.gnu.org, emacs-orgmode@gnu.org > From: Ihor Radchenko > Date: Tue, 05 Sep 2023 10:29:20 + > > As I described in the above, Org needs more control over the behaviour of > `kill-line'/`kill-whole-line' when the visible line contains multiple > lines of hidden text - to

Re: bug#59882: Multiple versions of Org in load-path problem

2023-02-21 Thread Eli Zaretskii
> Cc: emacs-orgmode@gnu.org, 59...@debbugs.gnu.org > From: Richard Stallman > Date: Tue, 21 Feb 2023 00:22:04 -0500 > > > >> I don't run Debian or Ubuntu anymore. However, I do recall that debian > > >> does use a modified Emacs startup which is not part of the standard > > >> Emacs

Re: bug#59882: Multiple versions of Org in load-path problem

2023-02-03 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: Stefan Monnier , emacs-orgmode@gnu.org, Eli > Zaretskii , 59...@debbugs.gnu.org > Date: Fri, 03 Feb 2023 11:02:21 + > > Considering the popularity of Debian-based distros, may someone take a > closer look on what may be going on? Since the

Re: bug#59882: Multiple versions of Org in load-path problem

2022-12-14 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: David Masterson , emacs-orgmode@gnu.org, > mic...@schi.nz, 59...@debbugs.gnu.org > Date: Wed, 14 Dec 2022 09:51:01 + > > On a related note, is it normal that package like org-mouse.el gets > loaded upon calling C-h f org-mouse- completion prompt? > org-mouse.el

Re: bug#59882: Multiple versions of Org in load-path problem

2022-12-09 Thread Eli Zaretskii
> From: David Masterson > Cc: Eli Zaretskii , "mic...@schi.nz" , > "emacs-orgmode@gnu.org" , "59...@debbugs.gnu.org" > <59...@debbugs.gnu.org> > Date: Fri, 09 Dec 2022 11:51:29 -0800 > > > https://www.gnu.org/software/emacs/man

Re: bug#59882: Multiple versions of Org in load-path problem

2022-12-09 Thread Eli Zaretskii
> From: David Masterson > Cc: mic...@schi.nz, emacs-orgmode@gnu.org, 59...@debbugs.gnu.org > Date: Thu, 08 Dec 2022 23:43:05 -0800 > > Eli Zaretskii writes: > > >> So, 'describe-variable' on org-version causes Org to be loaded?!? > > > > Why is it so

Re: bug#59882: Multiple versions of Org in load-path problem

2022-12-08 Thread Eli Zaretskii
> Cc: emacs-orgmode@gnu.org, 59...@debbugs.gnu.org > From: David Masterson > Date: Thu, 08 Dec 2022 13:56:03 -0800 > > In my testing, I found a strange case where, in *scratch*, I get: > > (message "%s" org-version) > ;; Error undefined > ;; Do 'C-h v org-version' > (message "%s" org-version) >

bug#35453: 26.1; Poor performance of vertical-motion in large org buffer

2022-10-29 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: Eli Zaretskii , 35...@debbugs.gnu.org > Date: Sat, 29 Oct 2022 09:02:31 + > > Ihor Radchenko writes: > > >> There are no intervals in this story. The way overlays are > >> implemented, they don't use intervals (if

Re: [CLOSED] text-property displayed image has a center-line when the text face has underline attribute

2022-10-02 Thread Eli Zaretskii
> From: Ihor Radchenko > Date: Sun, 2 Oct 2022 18:57:56 +0800 > Cc: Eli Zaretskii , emacs-de...@gnu.org, emacs-orgmode@gnu.org > > 1. find an image file in your system > 2. emacs -Q > 3. M-: (erase-buffer) > 4. Insert "askdjaklsdj lasasd" > 5. M-: (require

Re: [CLOSED] text-property displayed image has a center-line when the text face has underline attribute

2022-10-02 Thread Eli Zaretskii
> From: "Christopher M. Miles" > Cc: numbch...@gmail.com, yanta...@gmail.com, emacs-de...@gnu.org, > emacs-orgmode@gnu.org > Date: Sun, 02 Oct 2022 18:45:41 +0800 > > I hate to rewrite those steps more than 3 times. The problem is, I've read the correspondence on the Org list, and I still

Re: Fwd: [BUG] text-property displayed image has a center-line when the text face has underline attribute

2022-10-02 Thread Eli Zaretskii
> From: "Christopher M. Miles" > Cc: "Christopher M. Miles" , Org Mode > > Date: Sun, 02 Oct 2022 15:03:26 +0800 > > Ihor Radchenko writes: > > > "Christopher M. Miles" writes: > > > >> I replaced step 5 with step 6 by extracting the logic code of > >> org-link-beautify, but I found it does

Re: bug#45915: 28.2; delete-char deletes two letters

2022-09-23 Thread Eli Zaretskii
> Date: Fri, 23 Sep 2022 06:36:58 +0900 (JST) > Cc: yanta...@gmail.com, homeros.mis...@gmail.com, 45...@debbugs.gnu.org, > emacs-orgmode@gnu.org, t...@misasa.okayama-u.ac.jp > From: Tak Kunihiro > > >>> One other possibility is to use a slightly different :relative-width > >>> factor for the

Re: bug#45915: 28.2; delete-char deletes two letters

2022-09-22 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: homeros.mis...@gmail.com, t...@misasa.okayama-u.ac.jp, > 45...@debbugs.gnu.org, emacs-orgmode@gnu.org > Date: Thu, 22 Sep 2022 20:03:55 +0800 > > Eli Zaretskii writes: > > > One other possibility is to use a slightly different

bug#55342: 29.0.50; org-cite-basic--get-field: Wrong value for ENTRY-OR-KEY: nil

2022-05-10 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: Kaushal Modi , 55...@debbugs.gnu.org > Date: Tue, 10 May 2022 12:52:52 +0800 > > Eli Zaretskii writes: > > >> From: Kaushal Modi > >> Date: Mon, 9 May 2022 17:41:32 -0400 > >> > >> Exporting an Org file with

bug#55342: 29.0.50; org-cite-basic--get-field: Wrong value for ENTRY-OR-KEY: nil

2022-05-09 Thread Eli Zaretskii
> From: Kaushal Modi > Date: Mon, 9 May 2022 17:41:32 -0400 > > Exporting an Org file with citations on Emacs 29 now throws the error > "Wrong value for ENTRY-OR-KEY: nil". This error can be reproduced with > the Org version shipped with Emacs on the master branch. Shouldn't this be reported to

Re: bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones

2022-04-21 Thread Eli Zaretskii
> Date: Thu, 21 Apr 2022 16:56:25 -0700 > Cc: maniku...@gmail.com, emacs-orgmode@gnu.org, 54...@debbugs.gnu.org, > bug-gnu...@gnu.org > From: Paul Eggert > > What appears to be happening here is that the MS-Windows native > timestamp resolution is 1/64th of a second, and your system's clock is

Re: bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones

2022-04-21 Thread Eli Zaretskii
> Date: Wed, 20 Apr 2022 17:11:34 -0700 > Cc: maniku...@gmail.com, emacs-orgmode@gnu.org, 54...@debbugs.gnu.org, > bug-gnu...@gnu.org > From: Paul Eggert > > On 4/20/22 12:30, Eli Zaretskii wrote: > > > I see the time samples change in jumps of 15 msec. > &

Re: bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones

2022-04-20 Thread Eli Zaretskii
> Date: Wed, 20 Apr 2022 12:23:43 -0700 > Cc: maniku...@gmail.com, emacs-orgmode@gnu.org, 54...@debbugs.gnu.org, > bug-gnu...@gnu.org > From: Paul Eggert > > On 4/20/22 12:14, Eli Zaretskii wrote: > > Sorry, my bad. The result is the same, but I do get printouts. What

Re: bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones

2022-04-20 Thread Eli Zaretskii
> Date: Wed, 20 Apr 2022 11:19:29 -0700 > Cc: maniku...@gmail.com, emacs-orgmode@gnu.org, 54...@debbugs.gnu.org, > Gnulib bugs > From: Paul Eggert > > > Thanks, the test-gettime-res test says "gettime_res returned 625000 > > ns", which is a strange number: it doesn't fit any MS-Windows

Re: bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones

2022-04-20 Thread Eli Zaretskii
> Date: Wed, 20 Apr 2022 12:01:27 -0700 > Cc: maniku...@gmail.com, emacs-orgmode@gnu.org, 54...@debbugs.gnu.org, > bug-gnu...@gnu.org > From: Paul Eggert > > > I get the same result, and moreover I see no differences between this > > and the previous tarball, and no printouts in

Re: bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones

2022-04-20 Thread Eli Zaretskii
> Date: Tue, 19 Apr 2022 15:22:29 -0700 > Cc: maniku...@gmail.com, emacs-orgmode@gnu.org, 54...@debbugs.gnu.org > From: Paul Eggert > > On 4/18/22 22:50, Eli Zaretskii wrote: > >> * admin/merge-gnulib (GNULIB_MODULES): Add gettime-res. > >> * lib/gettime-re

Re: bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones

2022-04-18 Thread Eli Zaretskii
> Date: Mon, 18 Apr 2022 19:02:03 -0700 > From: Paul Eggert > Cc: emacs-orgmode@gnu.org, 54...@debbugs.gnu.org > > From 8c25372709d256d83858be454987137dc202b725 Mon Sep 17 00:00:00 2001 > From: Paul Eggert > Date: Mon, 18 Apr 2022 13:08:27 -0700 > Subject: [PATCH 3/6] Add Gnulib gettime-res

bug#53393: 29.0.50; org mode timestamp C-c C-c not updating day of week

2022-01-21 Thread Eli Zaretskii
> From: "Bruce E. Robertson" > Date: Tue, 18 Jan 2022 10:36:22 -0800 > > > emacs -Q test.org > cursor to "CLOCK:" line, C-c C-c > total time updates but day of week does not change > contents of test.org > -- > * heading > :LOGBOOK: > CLOCK: [2022-01-17 Tue 10:29]--[2022-01-19 Tue 10:29] =>

bug#12972: [PATCH] Avoid regression in mailcap-view-file similar to Bug#44824

2021-07-05 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Mon, 5 Jul 2021 20:12:34 +0700 > > It is about proper way to a launch viewer in > `mailcap-view-file'. Original `start-process-shell-command' with 'pty > connection type prematurely kills children of kde-open5 or gio open. > With 'pipe connection type it or

bug#12972: [PATCH] Avoid regression in mailcap-view-file similar to Bug#44824

2021-07-04 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Sun, 4 Jul 2021 20:37:24 +0700 > > I admit that I wrongly added ":noquery t", for some reason I believed > that it allows to choose whether processes are allowed to exist longer > than emacs or it is preferred to kill them with emacs. Actually > asynchronous

bug#12972: [PATCH] Avoid regression in mailcap-view-file similar to Bug#44824

2021-07-03 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Sat, 3 Jul 2021 18:29:30 +0700 > > I am giving up with this issue. That's too bad. I see no reason to give up, and I urge you to reconsider, please. > >> Because of I can not imagine such case for mailcap handler in Emacs yet > >> and, accordingly to you, "this

bug#12972: [PATCH] Avoid regression in mailcap-view-file similar to Bug#44824

2021-07-02 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Fri, 2 Jul 2021 23:24:23 +0700 > > On 02/07/2021 19:37, Eli Zaretskii wrote: > >> From: Maxim Nikulin > >> Date: Fri, 2 Jul 2021 19:21:55 +0700 > >> Cc: Lars Ingebrigtsen > >> > >>> And with other h

bug#12972: [PATCH] Avoid regression in mailcap-view-file similar to Bug#44824

2021-07-02 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Fri, 2 Jul 2021 19:21:55 +0700 > Cc: Lars Ingebrigtsen > > > And with other handlers, this could be an > > incompatible behavior change if the handler behaves differently when > > its standard handles are connected to a pipe rather than a terminal > > device. > >

bug#12972: [PATCH] Avoid regression in mailcap-view-file similar to Bug#44824

2021-07-01 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Fri, 2 Jul 2021 00:01:59 +0700 > > --- a/lisp/net/mailcap.el > +++ b/lisp/net/mailcap.el > @@ -1177,7 +1177,23 @@ See \"~/.mailcap\", `mailcap-mime-data' and related > files and variables." > (shell-quote-argument (convert-standard-filename file))

bug#48149: 27.2; Wrong underline width when the line char has a width of 2

2021-05-02 Thread Eli Zaretskii
> From: Nicolas Goaziou > Date: Sun, 02 May 2021 18:08:50 +0200 > Cc: 48...@debbugs.gnu.org > > > In case of 1), it correctly takes account of the case in which the character > > has a width of 2 in `org-ascii--build-title', by dividing the line width by > > `(char-width under-char)' (line

bug#48148: 27.2; ox-ascii breaks TITLE line wrongly when 2 width char is used

2021-05-02 Thread Eli Zaretskii
> From: Nicolas Goaziou > Cc: shingo@gmail.com, 48148-d...@debbugs.gnu.org > Date: Sun, 02 May 2021 17:56:04 +0200 > > More than the width of the text, I'm interested in the > ratio between the width of the text and the width of an underline > character (assuming monospace). And that is

bug#48148: 27.2; ox-ascii breaks TITLE line wrongly when 2 width char is used

2021-05-02 Thread Eli Zaretskii
> From: Nicolas Goaziou > Cc: shingo@gmail.com, 48...@debbugs.gnu.org > Date: Sun, 02 May 2021 14:18:24 +0200 > > My problem is that I have some string, _which is not displayed anywhere_ > yet. I need to obtain its real width along with the width of a single > character in order to compute

bug#48148: 27.2; ox-ascii breaks TITLE line wrongly when 2 width char is used

2021-05-02 Thread Eli Zaretskii
> Date: Sun, 02 May 2021 20:33:23 +0900 > From: Shingo Tanaka > Cc: Nicolas Goaziou , > shingo@gmail.com, > 48...@debbugs.gnu.org > > This bug (bug#48148) is actually caused by the difference of the width > detection methods between line 1036 in ox-ascii.el (`length') and >

bug#48149: 27.2; Wrong underline width when the line char has a width of 2

2021-05-02 Thread Eli Zaretskii
> From: Rudolf Schlatte > Date: Sun, 02 May 2021 10:36:14 +0200 > > > You reported a similar bug already, and I replied there that TRT in > > these cases is to use window-text-pixel-size, which will automatically > > account for the actual width on display of any characters and any > > fonts

bug#48148: 27.2; ox-ascii breaks TITLE line wrongly when 2 width char is used

2021-05-02 Thread Eli Zaretskii
> From: Nicolas Goaziou > Cc: Shingo Tanaka , 48...@debbugs.gnu.org > Date: Sun, 02 May 2021 10:23:34 +0200 > > > The accurate method of lining up in these cases is to use > > window-text-pixel-size instead. That function will return the exact > > width of a string as it will displayed, in

bug#48149: 27.2; Wrong underline width when the line char has a width of 2

2021-05-02 Thread Eli Zaretskii
> Date: Sun, 02 May 2021 10:12:43 +0900 > From: Shingo Tanaka > > When exporting org-mode document to plain text (either ascii/unicode/utf-8) > with `org-export-dispatch', Emacs inserts lines under headlines, inline > tasks, table rows and titles of the document, TOC, list of listings, list of >

bug#48148: 27.2; ox-ascii breaks TITLE line wrongly when 2 width char is used

2021-05-02 Thread Eli Zaretskii
> Date: Sun, 02 May 2021 08:52:13 +0900 > From: Shingo Tanaka > > For example, when the title is "ABCDEF" (each character has width of > 2), expected title would be like: > > ━━━ > ABCDEF > ━━━ > >

bug#44824: [PATCH] org.el: Avoid xdg-open silent failure

2021-02-19 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Fri, 19 Feb 2021 19:29:49 +0700 > Cc: 44...@debbugs.gnu.org > > > On Windows Emacs always uses pipes, because we don't have PTYs there. > > And there's no xdg-open on MS-Windows anyway, so it's a moot point. > > Should I consider your response as a suggestion to

bug#44824: [PATCH] org.el: Avoid xdg-open silent failure

2021-02-18 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Thu, 18 Feb 2021 19:56:03 +0700 > Cc: 44...@debbugs.gnu.org > > I could not estimate effect of such change on windows, so pipe process > is used only on linux. I am unsure concerning mac however. On Windows Emacs always uses pipes, because we don't have PTYs there.

bug#44824: 27.1; Org export as pdf and open file does not open it

2021-01-31 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Sun, 31 Jan 2021 22:57:57 +0700 > Cc: 44...@debbugs.gnu.org > > >> To fix the problem it is better to use (make-process :connection-type > >> 'pipe ...) that unfortunately has no higher level wrappers. > > > > Wouldn't it work to let-bind process-connection-type to

bug#44824: 27.1; Org export as pdf and open file does not open it

2021-01-31 Thread Eli Zaretskii
> From: Andreas Schwab > Cc: Maxim Nikulin , 44...@debbugs.gnu.org, > gbio...@gmail.com > Date: Sun, 31 Jan 2021 16:17:46 +0100 > > On Jan 31 2021, Eli Zaretskii wrote: > > > And I still don't understand why some people (like Lars) cannot > > reproduce the p

bug#44824: 27.1; Org export as pdf and open file does not open it

2021-01-31 Thread Eli Zaretskii
> From: Maxim Nikulin > Cc: Eli Zaretskii , gbio...@gmail.com > Date: Sun, 31 Jan 2021 18:15:27 +0700 > > Now I see that the problem with eshell is the same. I am not familiar > with eshell, but it creates new shell process for every executed > command. Actual handler is k

bug#44824: 27.1; Org export as pdf and open file does not open it

2021-01-30 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Sat, 30 Jan 2021 22:58:06 +0700 > Cc: 44...@debbugs.gnu.org > > The problem is that emacs does not expect that kde-open5 and thus > xdg-open exits instantly. Why is that a problem, and how does it cause the invocation to fail, i.e. not show the file in question? >

bug#44824: 27.1; Org export as pdf and open file does not open it

2021-01-30 Thread Eli Zaretskii
> From: Maxim Nikulin > Date: Sat, 30 Jan 2021 20:31:53 +0700 > Cc: gbio...@gmail.com > > > How about asking the xdg-open developers to help us figure out the > > reason? Or, failing that, debug xdg-open in the problematic > > situations to find out what fails there and why? E.g., could it be

bug#44824: 27.1; Org export as pdf and open file does not open it

2021-01-30 Thread Eli Zaretskii
> From: Lars Ingebrigtsen > Date: Sat, 30 Jan 2021 07:09:50 +0100 > Cc: 44...@debbugs.gnu.org > > This works: > M-! xdg-open /tmp/test.pdf RET > > This doesn't work: > M-& xdg-open /tmp/test.pdf RET > > This doesn't work: > M-x shell RET xdg-open /tmp/test.pdf RET How about asking the

bug#45091: 27.1; M-x org-table-paste-rectangle

2020-12-08 Thread Eli Zaretskii
> From: João Távora > Cc: Eli Zaretskii , 45...@debbugs.gnu.org, > t...@misasa.okayama-u.ac.jp > Date: Tue, 08 Dec 2020 17:02:13 + > > I'm quite lost as to why this happens, of course, but it seems it's > always coming from syntax-ppss. When I evaluate that defi

bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options

2020-11-29 Thread Eli Zaretskii
> Date: Sun, 29 Nov 2020 19:29:18 +0300 > From: Jean Louis > Cc: daniela-s...@gmx.it, 44...@debbugs.gnu.org > > * Eli Zaretskii [2020-11-29 18:08]: > > Shouldn't this be reported to the Org developers? > > We have discussed that Org is part of Emacs and users sha

bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options

2020-11-29 Thread Eli Zaretskii
> From: daniela-s...@gmx.it > Date: Sat, 28 Nov 2020 22:34:07 +0100 > > I have identified a problem. Let a user set the files to be used for > Org Agenda in .emacs as follows, and consider the situation when the > file writing.rcl.org does not exist. > > (setq org-agenda-files >

Re: bug#42199: Suggestion: Offer Emacs manual, org-mode manual, org-guide in double-sided fashion for printing

2020-07-04 Thread Eli Zaretskii
> From: Jan Teubel > Date: Sat, 4 Jul 2020 12:44:09 + > > This email is not a bug report, but a polite suggestion to > provide/offer Emacs manual, org-mode manual and org-guide in > double-sided fashion for printing (PDF files). > > I would like to print out the whole Emacs manual, org-mode

bug#41584: 26.3; org-indent-mode's line-prefix text property flickers near overlays

2020-05-30 Thread Eli Zaretskii
> From: Kévin Le Gouguec > Cc: 41584-d...@debbugs.gnu.org, dgu...@yandex.ru > Date: Fri, 29 May 2020 22:32:11 +0200 > > (I guess xdisp.c is something we won't to touch with a 10-foot pole on > the release branch, especially for a bug that users have lived with for > so long?) Exactly.

bug#41584: 26.3; org-indent-mode's line-prefix text property flickers near overlays

2020-05-29 Thread Eli Zaretskii
> From: Kévin Le Gouguec > Cc: 41...@debbugs.gnu.org, dgu...@yandex.ru > Date: Fri, 29 May 2020 20:11:40 +0200 > > This time, instead of hitting RET, insert a pair of parentheses, and > wait blink-matching-delay seconds until the opening parenthesis stops > being highlighted. Before and after

bug#41584: 26.3; org-indent-mode's line-prefix text property flickers near overlays

2020-05-29 Thread Eli Zaretskii
> Date: Fri, 29 May 2020 10:12:27 +0300 > From: Eli Zaretskii > Cc: 41...@debbugs.gnu.org, dgu...@yandex.ru > > In fact, it's enough to type "M-x". Which is a clear sign that some > redisplay optimization kicks in where it shouldn't. And indeed, > setting inhib

Re: bug#41584: 26.3; org-indent-mode's line-prefix text property flickers near overlays

2020-05-29 Thread Eli Zaretskii
> From: Kévin Le Gouguec > Date: Thu, 28 May 2020 21:54:09 +0200 > Cc: emacs-orgmode@gnu.org, Dmitry Gutov > > - emacs -Q > - C-x C-f repro.org > - M-x org-indent-mode > - M-: (insert "* heading\ntext") > - M-: > (let ((ov (make-overlay (point-at-bol) (point-at-bol))) > (val (propertize "

bug#34684: 26.1; Strange characters when inserting date

2020-05-22 Thread Eli Zaretskii
> From: Bastien > Cc: "Wong, Philip" , rpl...@gmail.com, > 34...@debbugs.gnu.org > Date: Fri, 22 May 2020 14:10:21 +0200 > > It seems like the bug is not related to org-mode. It isn't, but it can also be closed. Which I did. Thanks.

Re: org 9.2.6 and org 9.1.9

2019-11-27 Thread Eli Zaretskii
> From: Stefan Kangas > Date: Wed, 27 Nov 2019 07:29:24 +0100 > Cc: Jean-Christophe Helary , > Org-mode , Emacs developers > > I disagree with removing Org-mode from Emacs core, as I've explained > elsewhere. I agree. It would go against our previous decisions to have Org in core, for

Re: [O] Emacs master, faces with :extend t let cursor vanish at EOL?!

2019-10-23 Thread Eli Zaretskii
> From: Kaushal Modi > Date: Tue, 22 Oct 2019 16:17:04 -0400 > Cc: emacs-org list , > Ingo Lohmar I suggest not to cross-post to 2 mailing lists. > The issue occurs because of the new :extend feature for faces to extend till > end of lines. > > With that enabled, I have also seen that the

[O] bug#35453: 26.1; Poor performance of vertical-motion in large org buffer

2019-05-05 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: 35...@debbugs.gnu.org > Date: Sun, 05 May 2019 09:05:46 +0800 > > > Of course, if someone comes up with ideas how to speed up > > vertical-motion without changing what Org does with overlays and/or > > how overlays are implemented, such ideas will be most

[O] bug#34684: bug#34684: 26.1; Strange characters when inserting date

2019-03-12 Thread Eli Zaretskii
> From: Takaaki Ishikawa > Date: Tue, 12 Mar 2019 12:42:39 +0900 > Cc: Robert Pluim , Eli Zaretskii , > "34...@debbugs.gnu.org" <34...@debbugs.gnu.org> > > Have you tried to use `set-local-environment'? > I usually use the command to change the date f

[O] bug#34684: 26.1; Strange characters when inserting date

2019-03-12 Thread Eli Zaretskii
> From: "Wong, Philip" > CC: "rpl...@gmail.com" , "34...@debbugs.gnu.org" > <34...@debbugs.gnu.org> > Date: Tue, 12 Mar 2019 09:58:17 + > > That did the job, thanks! OK, thanks. I guess we will need to try doing this automatically at startup...

[O] bug#34684: 26.1; Strange characters when inserting date

2019-03-11 Thread Eli Zaretskii
> From: "Wong, Philip" > CC: "rpl...@gmail.com" , "34...@debbugs.gnu.org" > <34...@debbugs.gnu.org> > Date: Mon, 11 Mar 2019 17:35:05 + > > Here is the output in the order of commands you mentioned: > <2019-03-11 ¬P´Á¤@> > > For the other commands, there is no output in the actual

[O] bug#34684: 26.1; Strange characters when inserting date

2019-03-11 Thread Eli Zaretskii
> From: "Wong, Philip" > CC: "rpl...@gmail.com" , "34...@debbugs.gnu.org" > <34...@debbugs.gnu.org> > Date: Mon, 11 Mar 2019 16:55:42 + > > Thanks Eli, you're right. > > I still get '<2019-03-11 ¶g¤@>' OK, as expected. This means Org is indeed off the hook, the problem is with

[O] bug#34684: 26.1; Strange characters when inserting date

2019-03-11 Thread Eli Zaretskii
> X-Spam-Status: No, score=3.3 required=5.0 tests=BAYES_50,RCVD_IN_DNSWL_NONE, > RECEIVED_FROM_WINDOWS_HOST,URIBL_BLOCKED autolearn=disabled > version=3.3.2 > From: "Wong, Philip" > CC: Eli Zaretskii , "34...@debbugs.gnu.org" > <34...@debbug

[O] bug#34684: 26.1; Strange characters when inserting date

2019-03-11 Thread Eli Zaretskii
> From: "Wong, Philip" > CC: "34...@debbugs.gnu.org" <34...@debbugs.gnu.org> > Date: Mon, 11 Mar 2019 09:41:41 + > > Sorry, I don't understand what you mean by emacs -Q. > > How exactly am I supposed to run this command? Open the Windows command window that runs cmd.exe, and type "emacs

[O] bug#34684: 26.1; Strange characters when inserting date

2019-03-11 Thread Eli Zaretskii
> From: "Wong, Philip" > CC: Eli Zaretskii , "34...@debbugs.gnu.org" > <34...@debbugs.gnu.org> > Date: Mon, 11 Mar 2019 10:47:00 + > > Does the same thing OK. Can you send the list of abbreviated weekdays in your locale's language, as y

[O] bug#34684: 26.1; Strange characters when inserting date

2019-03-01 Thread Eli Zaretskii
> From: Robert Pluim > Cc: philip.w...@warwick.ac.uk, 34...@debbugs.gnu.org > Date: Fri, 01 Mar 2019 15:25:04 +0100 > > We are miscommunicating. I was demonstrating that in my setup, > org-time-stamp produces the correct output => itʼs a configuration > issue. I'm not yet sure it's a

[O] bug#34684: 26.1; Strange characters when inserting date

2019-03-01 Thread Eli Zaretskii
> From: Robert Pluim > Cc: philip.w...@warwick.ac.uk, 34...@debbugs.gnu.org > Date: Fri, 01 Mar 2019 14:47:21 +0100 > > > That's only so if the above produces the same garbled result as in the > > original report. Does it? > > Didnʼt I send this yesterday? > > $ LANG=zh_HK src/emacs -Q -l

[O] bug#34684: 26.1; Strange characters when inserting date

2019-03-01 Thread Eli Zaretskii
> From: Robert Pluim > Cc: Eli Zaretskii , 34...@debbugs.gnu.org > Date: Fri, 01 Mar 2019 11:00:01 +0100 > > > It could be some snafu in Org, though, e.,g. if it doesn't know how to > > support that value of $LANG. In any case, should be reported to Org > > d

[O] bug#34684: 26.1; Strange characters when inserting date

2019-02-28 Thread Eli Zaretskii
> From: Robert Pluim > Cc: "Wong\, Philip" , 34...@debbugs.gnu.org > Date: Thu, 28 Feb 2019 20:11:45 +0100 > > Eli Zaretskii writes: > > >> From: "Wong, Philip" > >> Date: Thu, 28 Feb 2019 14:16:25 + > >> > >

[O] bug#34684: 26.1; Strange characters when inserting date

2019-02-28 Thread Eli Zaretskii
> From: "Wong, Philip" > Date: Thu, 28 Feb 2019 14:16:25 + > > When I insert a date by pressing CTRL+C then period then enter I get > “<2019-02-28 ¶g¥|>”. > > I’m not sure what the strange character is (¶g¥|), can someone help? Please show a complete recipe, starting from "emacs -Q", to

  1   2   3   >