From smbv-card.comjp-update at 0aleunte.cn Wed Dec 1 10:03:53 2021 From: smbv-card.comjp-update at 0aleunte.cn (Amazon.co.jp) Date: Wed, 1 Dec 2021 19:03:53 +0900 Subject: [Pkg-zsh-devel] =?utf-8?b?44CQU01CQyBDQVJE44CR44Kr44O844OJ44Gu?= =?utf-8?b?5LiA5pmC5Yip55So5YGc5q2i44Gv6Kej6Zmk44GV44KM44G+44GX44Gf?= =?utf-8?q?_37?= Message-ID: <006eee02fc39$4ec45159$e8ea3c28$@mcfyfmmjwz> ?????? ?????????????????????????????????????????????????? ??????????????IP?60.47.64.80??????IPHONE 11.?????????????? ????????????????????? ????????????? ????????????? ????????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From smbv-card.com-account-update at 0aleunte.cn Wed Dec 1 17:46:15 2021 From: smbv-card.com-account-update at 0aleunte.cn (Amazon.co.jp) Date: Thu, 2 Dec 2021 02:46:15 +0900 Subject: [Pkg-zsh-devel] =?utf-8?b?44CQU01CQyBDQVJE44CR44Kr44O844OJ44Gu?= =?utf-8?b?5LiA5pmC5Yip55So5YGc5q2i44Gv6Kej6Zmk44GV44KM44G+44GX44Gf?= =?utf-8?q?_37?= Message-ID: <00b2dbc25eb3$bf9268cb$5a35ec44$@xmpdk> ?????? ?????????????????????????????????????????????????? ??????????????IP?60.47.64.80??????IPHONE 11.?????????????? ????????????????????? ????????????? ????????????? ????????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at os.chernigiv-rada.gov.ua Wed Dec 1 22:52:10 2021 From: noreply at os.chernigiv-rada.gov.ua (Lisa Robinson) Date: Thu, 02 Dec 2021 06:52:10 +0800 Subject: [Pkg-zsh-devel] Charity Donation Message-ID: <20211201225231.28FED16C5901@gate.chernigiv-rada.gov.ua> Hello, be informed that you have been selected to benefit from a charity project aimed at touching lives as God has blessed me. The sum of $1,200,000.00 has been donated to you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From osamu at debian.org Thu Dec 9 11:58:58 2021 From: osamu at debian.org (Osamu Aoki) Date: Thu, 09 Dec 2021 20:58:58 +0900 Subject: [Pkg-zsh-devel] Bug#776663: zsh problem on wayland References: <20150130182521.26522.84348.reportbug@wllt1771.nerc-wallingford.ac.uk> Message-ID: <9f46d77f403b79a882aabeec754da9a0f9b8da88.camel@debian.org> Hi, I had a bug report on my package: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983116 The discussion had reference to this bug here > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776663 Let me share my thought here too ... In very good old days, as long as you keep your root and daemon's account in the default shell (bash?), you didn't have much problem with chsh on user account. I am sure people use to use csh this way. Even then, there were some advocacy to use ksh/bash compatible shell, I suppose, to ensure proper and successful environment variables setteing or something :-) Once people started using X, choosing csh as the login shell via chsh became non- option. But people had false sense that the traditional chsh mechanism is right way to change login shell among bash/zsh (or POSIX shells). Making Xsession.d scripts bash/zsh compatible caused several bugs and their fixes in my im-config package which is a thin glue layer to choose i18n GUI keyboard input mechanism offered by one of several input module frameworks (ibus, fcitx, uim, SCIM, ...). I think the root cause of the problem is we choose to parse these system startup scripts with the shell chosen effectively by chsh command for interactive shell. I mean shell set in /etc/passwd. Before X, as long as we don't change login shell for the root and other daemon program's accounts from bash, we had no problem. With X, we started to say POSIX shell (no csh) should be chosen by chsh. Now we are facing another problem with Wayland and how shell use their startup code. To me, non-interactive shell used by Xsession or and other system configuration should be separately configurable from whatever interactive shell user desired to use in /etc/passwd. /usr/bin/sh should be the one for non-interactive shell but if it is difficult initially, I can live with /uar/bin/bash instead. Until someone with lots of energy and (social and technical) skill decides to work on separating these 2 shells on Debian system, I strongly recommend people to set so- called "login shell" always to /usr/bin/bash. If you want to use other shells (zsh, csh, fish, ...) for INTERACTIVE use, the easiest solution is to set it in your terminal program. Then there is no COMPATIBILITY nor PISIX problem. If you want to use non-bash for SSHed host, I suppose, adding something along the following in ~/.baahrc should be able to set INTERACTIVE login shell to non-bash ones. --- # If not running interactively, don't do anything case $- in *i*) ;; *) return;; esac exec /usr/bin/zsh -i --- .... It would be great, if chsh is made to control interactive shell. Until we sort out separation of "non-interactive system configuration shell" and "interactive console shell", there will be bugs caused by the differences even among so-called accepted shells (POSIX). I don't think adding work around will never solve this bug prone situation. This will involve some coordination with systemd/pam things, I don't have high hope and motivation. If anyone does, I will be happy. Until then, all I can say is chsh is a historic tool which has no practical use. Just use basj and use practical solution I mentioned above. Good luck. Osamu From support-amazon.jp at tjzubai.cn Sat Dec 11 19:12:56 2021 From: support-amazon.jp at tjzubai.cn (Amazon.co.jp) Date: Sun, 12 Dec 2021 04:12:56 +0900 Subject: [Pkg-zsh-devel] =?utf-8?b?44CQQW1hem9u44CR44Ki44Kr44Km44Oz44OI?= =?utf-8?b?5oOF5aCx44KS44GU56K66KqN44GP44Gg44GV44GE?= Message-ID: <20211212041302018771@tjzubai.cn> Amazon??? ????Amazon?????????????????????? ????????????????????????????????? ?????????????????????????????? ????????? ???????? ????????????????????????????????????????????????????????? ????24??????????????????????????????Amazon????????????????? ?????????????????????????????? ????????????????? ???? Amazon ????? ??????????????????????Amazon ?????????????????????????????????????????????????????????????????? ??: ????????? Amazon????&???? Amazon?????????????????? ? 1996-2021, Amazon. Inc. or its affiliates -------------- next part -------------- An HTML attachment was scrubbed... URL: From web.office.prestamo.loan at gmail.com Tue Dec 21 01:44:15 2021 From: web.office.prestamo.loan at gmail.com (David Wayne) Date: Mon, 20 Dec 2021 19:44:15 -0600 Subject: [Pkg-zsh-devel] (no subject) Message-ID: -- Loan Offer!! Do you need a loan? if yes, reply for more information... INFORMATION Name: Amount: Duration: Country: Phone Number: we offer loan at low interest rate of 3% contact us today if you are interesting in receive the loan From david at tethera.net Sun Dec 26 11:54:35 2021 From: david at tethera.net (David Bremner) Date: Sun, 26 Dec 2021 07:54:35 -0400 Subject: [Pkg-zsh-devel] Bug#941214: mutt zsh completion broken, -a does not take email address In-Reply-To: <87mtkricdi.fsf@tethera.net> References: <20190926143542.GA10552@albatross.lehel.madduck.net> <20190926143542.GA10552@albatross.lehel.madduck.net> <87mtkricdi.fsf@tethera.net> Message-ID: <87mtknmvic.fsf@tethera.net> David Bremner writes: > martin f krafft writes: > >> Package: notmuch >> Version: 0.29.1-2 >> Severity: normal >> File: /usr/share/zsh/vendor-completions/_email-notmuch >> >> mutt has a command-line switch '-a' for attachments, and the Zsh >> completer offers files and directories for its argument. >> >> As of late, _email-notmuch also adds all addresses into the mix: >> >> % mutt -a ^D >> directory >> [?] >> file attachment >> [?] >> email address (notmuch) >> [?] >> >> >> In the context of '-a', no email addresses should be offered. Maybe >> this is actually a problem with Zsh or Mutt, I can't figure it out. >> But since I see mainly notmuch in the output, I am filing here? > > As far as I can tell, the whole point of _email-notmuch is to provide > addresses, so maybe it shouldn't be called there? To me that suggests > the bug should be reassigned to mutt. I am CCing the mutt maintainers, > in case they want to weigh in. > > d My mistake, the mutt completion is actually shipped by zsh. I've attached _email-notmuch (installed by package notmuch) for feedback. If something looks wrong with it, please let me know. Otherwise I think I should reassign this bug to zsh, where it can at least get some more expert consideration. -------------- next part -------------- A non-text attachment was scrubbed... Name: _email-notmuch Type: application/octet-stream Size: 239 bytes Desc: not available URL: From abe at debian.org Thu Dec 30 08:33:16 2021 From: abe at debian.org (Axel Beckert) Date: Thu, 30 Dec 2021 09:33:16 +0100 Subject: [Pkg-zsh-devel] Why does zsh-static depend on zsh? (And: Dropping debian/zsh-static.NEWS) Message-ID: <20211230083310.xwdt3t4w6xia7l2u@sym.noone.org> Hi, I just wondered why our zsh-static package depends on the zsh package. Using git blame I traced that dependency back to this commit: commit 78ab02ffa00d1f1a149bed755b72ff0bf0ff4bbb Author: Frank Terbeck Date: Fri Feb 11 15:59:00 2011 +0100 Initial `debian/' import In other words: It's in there since before the Debian Zsh Team was founded. Cc'ing Clint in the hope that he still remembers what the reason for this dependency was. At least I didn't find any hint on this dependency in debian/changelog. I also checked https://snapshot.debian.org/binary/zsh-static/ if it still has the first zsh-static package (4.0.0+4.0.1.pre4-4 from May 2001), but Debian Snapshots only reaches back to 4.0.4-33 from April 2002 (imported into Snapshots in 2009). But at least 4.0.4-33 already has that dependency, so I suspect that this dependency was in there from the birth of the zsh-static package a year before that upload. I kinda suspect that it can be replaced nowadays by a dependency on zsh-common (see also below for another hint towards that direction) or maybe even completely removed. I'll probably do a test in a clean chroot by installing zsh-static and then doing a "dpkg --purge --force-depends zsh" or so. Apropos zsh-static: While looking through debian/changelog for "zsh-static", I stumbled upon this entry from 2015: * [01eea476] Add debian/zsh-static.NEWS with note about upcoming zsh-static removal. It says: zsh (5.0.7-dev-2-1) experimental; urgency=low * zsh-static will go away soon. Object now if you need it and tell us why at pkg-zsh-devel at lists.alioth.debian.org. See also http://noone.org/blog?-tags=zsh-static -- Axel Beckert Tue, 05 May 2015 12:09:14 +0200 I actually forgot about that plan even though we recently had a zsh-static vs libc fight once again. I checked our feedback on that blog-posting and we seem to have gotten at least two some positive (well, one positive and one rather weird ;-) feedback about zsh-static. One specific zsh-static feedback from Vincent Bernat might even give an answer on my initial question: > I am using zsh-static. This way, I am able to inject into almost any > docker image that I want to use as a sandbox. I also bind-mount > /usr/share/zsh in this case. I don't care about the user/group > lookup for this case. So I checked which package ship files in /usr/share/zsh/. And it's not zsh but zsh-common. So I guess I just oversaw that /usr/share/zsh/ was likely the reason for that unclear zsh-static dependency on zsh when splitting out the zsh-common package from the zsh package. But back to the zsh-static removal topic: Also the occasional bug reports about zsh-static, like the recent https://bugs.debian.org/993843 show that there are active users despite a slowly sinking popcon: https://qa.debian.org/popcon-graph.php?packages=zsh-static&show_installed=on&show_vote=on&want_legend=on&date_fmt=%25Y-%25m&beenhere=1 So I just decided to drop that debian/zsh-static.NEWS entry from 6 years ago and keep fighting zsh-static vs libc bugs as Clint already did back in 2003: https://bugs.debian.org/207218 ? "changes in libc cause zsh-static to immediately segfault" :-) I'll probably not do an upload with that commit immediately, but it will be part of the next source upload whenever that will be. So if anyone wants to object and still warn our users about a future zsh-static removal, please do so now. :-) Another thing I'll do is to extend the zsh-static package description as one of the (neutral) feedbacks on the zsh-static removal proposal was a question from shirish what the difference between zsh and zsh-static is. I'll take a bit of text from my answer to that question and put it into the zsh-static long package description. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From danielsh at apache.org Fri Dec 31 02:16:19 2021 From: danielsh at apache.org (Daniel Shahaf) Date: Fri, 31 Dec 2021 02:16:19 +0000 Subject: [Pkg-zsh-devel] Bug#941214: mutt zsh completion broken, -a does not take email address In-Reply-To: <87mtknmvic.fsf@tethera.net> References: <20190926143542.GA10552@albatross.lehel.madduck.net> <20190926143542.GA10552@albatross.lehel.madduck.net> <87mtkricdi.fsf@tethera.net> <87mtknmvic.fsf@tethera.net> Message-ID: <20211231021619.GB4971@tarpaulin.shahaf.local2> David Bremner wrote on Sun, Dec 26, 2021 at 07:54:35 -0400: > David Bremner writes: > > > martin f krafft writes: > > > >> Package: notmuch > >> Version: 0.29.1-2 > >> Severity: normal > >> File: /usr/share/zsh/vendor-completions/_email-notmuch > >> > >> mutt has a command-line switch '-a' for attachments, and the Zsh > >> completer offers files and directories for its argument. > >> > >> As of late, _email-notmuch also adds all addresses into the mix: > >> > >> % mutt -a ^D > >> directory > >> [?] > >> file attachment > >> [?] > >> email address (notmuch) > >> [?] > >> > >> > >> In the context of '-a', no email addresses should be offered. Maybe > >> this is actually a problem with Zsh or Mutt, I can't figure it out. > >> But since I see mainly notmuch in the output, I am filing here? > > > > As far as I can tell, the whole point of _email-notmuch is to provide > > addresses, so maybe it shouldn't be called there? To me that suggests > > the bug should be reassigned to mutt. I am CCing the mutt maintainers, > > in case they want to weigh in. > > > > d > > My mistake, the mutt completion is actually shipped by zsh. I've > attached _email-notmuch (installed by package notmuch) for feedback. If > something looks wrong with it, please let me know. Otherwise I think I > should reassign this bug to zsh, where it can at least get some more > expert consideration. By code inspection: Email addresses are offered because the function _mutt (from the file of the same name shipped by zsh-common) contains: . _arguments -s -S \ '::recipient:_email_addresses -n mutt' \ '*-a[attach file using MIME]::file attachment:_files' \ . which is as self-explanatory as it gets, of course ? The two consecutive colons on the -a line mean the -a option takes an optional argument. Therefore, ?mutt -a ? completes both arguments to -a, using _files, and email addresses, using ?_email_addresses -n mutt? (which presumably calls _email-notmuch along with other _email-* functions). Still by code inspection, if you remove one of the two consecutive colons on the -a line, email addresses shouldn't be offered any more. If the above analysis is correct, this bug report belongs to zsh-common. Furthermore, if invocations such as ?mutt -a foo at example.com? and ?mutt -a? without further arguments are errors (they are in older mutts, but I haven't tested in sid), then the report is valid and the fix would be to drop the second consecutive colon from the -a line in _mutt. Cheers, Daniel From madduck at debian.org Fri Dec 31 02:26:24 2021 From: madduck at debian.org (martin f krafft) Date: Fri, 31 Dec 2021 15:26:24 +1300 Subject: [Pkg-zsh-devel] Bug#941214: mutt zsh completion broken, -a does not take email address In-Reply-To: <20211231021619.GB4971@tarpaulin.shahaf.local2> References: <20190926143542.GA10552@albatross.lehel.madduck.net> <20190926143542.GA10552@albatross.lehel.madduck.net> <87mtkricdi.fsf@tethera.net> <87mtknmvic.fsf@tethera.net> <20211231021619.GB4971@tarpaulin.shahaf.local2> Message-ID: Regarding the following, written by "Daniel Shahaf" on 2021-12-31 at 02:16 Uhr +0000: >The two consecutive colons on the -a line mean the -a option takes >an optional argument. Herein lies the problem: ``` -a [...] -- attach file(s) to the message the list of files must be terminated with the "--" sequence ``` So it's neither optional, nor even a single word by necessity. -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems "the college students who are using lsd and marijuana today do not comprise a criminal class. they are not drug addicts seeking to escape. they're your best educated, your most creative, and your most couragious, young people. and like it or not, they might build you a new civilisation." -- porcupine tree, voyage 34 -------------- next part -------------- An HTML attachment was scrubbed... URL: From danielsh at apache.org Fri Dec 31 03:13:07 2021 From: danielsh at apache.org (Daniel Shahaf) Date: Fri, 31 Dec 2021 03:13:07 +0000 Subject: [Pkg-zsh-devel] Bug#941214: mutt zsh completion broken, -a does not take email address In-Reply-To: References: <20190926143542.GA10552@albatross.lehel.madduck.net> <20190926143542.GA10552@albatross.lehel.madduck.net> <87mtkricdi.fsf@tethera.net> <87mtknmvic.fsf@tethera.net> <20211231021619.GB4971@tarpaulin.shahaf.local2> Message-ID: <20211231031307.GD4971@tarpaulin.shahaf.local2> martin f krafft wrote on Fri, Dec 31, 2021 at 15:26:24 +1300: > Regarding the following, written by "Daniel Shahaf" on 2021-12-31 at 02:16 Uhr +0000: > > The two consecutive colons on the -a line mean the -a option takes an > > optional argument. > > Herein lies the problem: > > ``` > -a [...] -- attach file(s) to the message > the list of files must be terminated with the "--" sequence > ``` > > So it's neither optional, nor even a single word by necessity. Good catch. I think it's possible to teach _mutt how to complete this in the general case, but the details are better hashed out upstream (zsh-workers at zsh.org). Cheers, Daniel From owner at bugs.debian.org Fri Dec 31 11:03:03 2021 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 31 Dec 2021 11:03:03 +0000 Subject: [Pkg-zsh-devel] Processed: reassign 941214 to zsh-common References: <1640948520-387-bts-bremner@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > reassign 941214 zsh-common Bug #941214 [notmuch] mutt zsh completion broken, -a does not take email address Bug reassigned from package 'notmuch' to 'zsh-common'. No longer marked as found in versions notmuch/0.29.1-2. Ignoring request to alter fixed versions of bug #941214 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 941214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941214 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From owner at bugs.debian.org Fri Dec 31 11:15:05 2021 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 31 Dec 2021 11:15:05 +0000 Subject: [Pkg-zsh-devel] Processed: tagging 941214 References: <1640949021-2118-bts-abe@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > tags 941214 - moreinfo + upstream Bug #941214 [zsh-common] mutt zsh completion broken, -a does not take email address Removed tag(s) moreinfo. Bug #941214 [zsh-common] mutt zsh completion broken, -a does not take email address Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 941214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941214 Debian Bug Tracking System Contact owner at bugs.debian.org with problems