unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rahguzar <rahguzar@zohomail.eu>
To: Rahguzar <rahguzar@zohomail.eu>
Cc: Michael Albinus <michael.albinus@gmx.de>,
	Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: master 84e4bc6219a 1/2: Add input methods for Urdu, Pashto and Sindhi (bug#66470)
Date: Sun, 21 Jan 2024 16:07:31 +0100	[thread overview]
Message-ID: <87le8ira14.fsf@zohomail.eu> (raw)
In-Reply-To: <87plxuravt.fsf@zohomail.eu>

Actually I see what is happening now. `cus-test-deps` is checking if it
can load the files defining the custom variables. None of the files in
lisp/leim/quail are on the load path. The cases where require succeeds
it is because some other file with the same file-name-non-directory is
on the load path e.g. for indian.el it is,

lisp/language/indian.el

which does not define any custom variable.

I think the problem is with the test.

P.S. Both lisp/leim/quail/indian.el and lisp/language/indian.el provide
the feature indian which doesn't seem like the right thing.

Rahguzar <rahguzar@zohomail.eu> writes:

> Hi Michael,
>
> Michael Albinus <michael.albinus@gmx.de> writes:
>
>> Rahguzar <rahguzar@zohomail.eu> writes:
>>
>>> Hi Michael,
>>
>> Hi Rahguzar,
>>
>>> So I wonder if the test is encouraging the correct behavior. I think
>>> that seeing the `pakistan-urdu-input` subgroup would be useful for
>>> people using `urdu-custom` input method but perhaps for majority of
>>> people we shouldn't cause pakistan.el to load just because they wanted
>>> to customize a quail option.
>>>
>>> Maybe it is better to just remove `quail` as the parent group of
>>> `pakistan-urdu-input`?
>>
>> No idea. Note, that there is also lisp/leim/quail/indian.el. It declares
>> defgroup `tamil-input', and it doesn't show an error in the test.
>>
>> I've tried to replace the parent group of `pakistan-urdu-input' to be
>> `leim' instead of `quail'. But the error about the missing pakistan.el
>> persists, just using `leim' instead of `quail' in the error message.
>
> Poking around `cus-test.el` a little I think this is a load path problem
> and unrelated to the defgroup form.
>
> I can run
>
> src/emacs -batch --eval="(require 'indian)"
>
> in a shell and it exists without any error.
>
> But
>
> src/emacs -batch --eval="(require 'pakistan)"
>
> results in
>
> Error: file-missing ("Cannot open load file" "No such file or directory" "pakistan")
>   mapbacktrace(#f(compiled-function (evald func args flags) #<bytecode -0x188ce6540514dc1>))
>   debug-early-backtrace()
>   debug-early(error (file-missing "Cannot open load file" "No such file or directory" "pakistan"))
>   require(pakistan)
>   eval((require 'pakistan) t)
>   command-line-1(("--eval=(require 'pakistan)"))
>   command-line()
>   normal-top-level()
> Cannot open load file: No such file or directory, pakistan
>
> Similarly starting with
>
> src/emacs -Q
>
> M-: (require 'indian) RET
>
> works
>
> but
>
> M-: (require 'pakistan) RET
>
> doesn't.
>
> Neither do any of,
>
> M-: (require 'ipa) RET
> M-: (require 'uni-input) RET
>
> If fact there are 10 files in lisp/leim/quail with provide forms.
>
> Out of these requiring one philippine, indonesian, indian, misc-lang and
> emoji succeeds.
>
> While requiring one of uni-input, rfc1345, compose, pakistan or hangul
> leads to an error.
>
> I don't know why this is the case.
>
>> Best regards, Michael.
>
> Rahguzar



  reply	other threads:[~2024-01-21 15:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <170030013667.20571.18090141972402319489@vcs2.savannah.gnu.org>
     [not found] ` <20231118093537.9F147C0C994@vcs2.savannah.gnu.org>
2024-01-19  8:45   ` master 84e4bc6219a 1/2: Add input methods for Urdu, Pashto and Sindhi (bug#66470) Michael Albinus
2024-01-19 20:59     ` Rahguzar
2024-01-20 10:17     ` Eli Zaretskii
2024-01-20 11:16       ` Rahguzar
2024-01-20 11:30       ` Rahguzar
2024-01-20 11:58         ` Eli Zaretskii
2024-01-20 12:12           ` Rahguzar
2024-01-21 11:19       ` Michael Albinus
2024-01-21 12:34         ` Rahguzar
2024-01-21 13:21           ` Michael Albinus
2024-01-21 14:35             ` Rahguzar
2024-01-21 15:07               ` Rahguzar [this message]
2024-01-21 18:16                 ` Michael Albinus
2024-01-22  5:10                   ` Visuwesh
2024-01-22  8:24                     ` Michael Albinus
2024-01-23 17:30                   ` Eli Zaretskii
2024-01-23 18:25                     ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87le8ira14.fsf@zohomail.eu \
    --to=rahguzar@zohomail.eu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).