Arch Linux User Repository

WeChat will soon split into 2 packages. While wechat-bin will be the new "vanilla" version, this package will revert back to the original state and automatically set env vars for input method, HiDPI and more. The sandbox will still remain optional in this package, though.

右键应用程序图标可与微信共享文件. 其将被放置在沙盒的 ~/Shared 中.

WeChat_Data/portable.env 中的环境变量将会自动导入至微信.

不支持纯 Wayland 环境, 微信并未构建 Wayland 模块.

若要查看使用手册, 访问 https://wiki.archlinuxcn.org/wiki/WeChat

For user manual and internal document, consult https://wiki.archlinux.org/title/WeChat

KDE Plasma 添加阴影

1.添加阴影

在微信界面，ALT+F3 -> 更多操作 -> 配置特殊窗口设置 -> 添加属性 -> 添加 外观和修正 下面的 无标题栏和边框 -> 将 初始状态应用 改为 强制，将后面的 是 切换称 否 -> 应用

2.去除标题栏

之后微信就有边框阴影了，但是微信多了个标题栏。

设置 -> 颜色和主题 -> 窗口装饰元素 -> 找到你在用的主题右下角的编辑 -> 切换到 特定窗口优先规则 -> 添加 -> 检测窗口属性... -> 选中微信窗口 直到 匹配正则表达式 那里出现 wechat -> 勾选 装饰选项 下面的 隐藏窗口标题栏 -> 确定 -> 应用

@yangling 没有. 我不认为 <30KiB 是很大的依赖

portable 有办法做到是可选包吗？不是很喜欢加太大三方的依赖

@Kimiblock Thx, it worked.

Then I wonder why months have passed with little to no progress. 🤔

I'd imagine it's not something like pretending that we did push the progress and call it a day.

@Kimiblock This indeed is an inappropriate usage of the "replaces" array. This should be a "conflicts" array at best.

As you know (since you started the related discussion on the ML), the "wechat packaging situation" in the AUR is a bit controversial and difficult to deal with.
Claiming legitimacy over the other existing packages in a forced and unexpected manner like you're doing is not helpful.

I switched the "replaces" array to a "conflicts" one, please do not switch it back and give time for the AUR staff to deal with the pending requests about wechat related packages.

Thanks for your comprehension & collaboration.

If you have any more concerns, contact me via mail.

Do not flood this area with useless comments.

Are you failing to catch my point again and again, or intentionally done just to define me as a rule breaker?

I do not want to be a repeater and replace is allowed when a package is subject to rename (merge)

@kimiblock to be clear, you're refusing to follow the AUR guidelines? You are also confusing replaces with conflicts.

Currently this package is maliciously replacing packages you want merged where other maintainers disagree.

@envolution I don’t think AUR helpers have the ability to replace packages yet. And you are avoiding the duplication fact.

Replaces here only stands as a statement that dupes should not be allowed and has no actual effect.

I should follow the guidelines only when others do. Or I see this as a double standard.

@Kimiblock The job of an AUR maintainer is not to force external packages to uninstall and be replaced by your own. If you cannot follow the guidelines, perhaps you are not a good fit for the task.

The guidelines are very clear for this exact reason.