Comments (10)
de-vri-es
commented on June 6, 2024
I'd love to help, but you're going to have to be more specific. I just updated to slack.py 2.6.0 from the built-in script manager and autosort.py still seems to work fine.
What exactly is broken? What did you expect to happen, but what happens instead? Are there any error messages?
from weechat-autosort.
dyipon
commented on June 6, 2024
well, I tried with latest (but not yet released) weechat, not with 2.6.0.
after I downgrade back to 2.6.0, it works again.
from weechat-autosort.
de-vri-es
commented on June 6, 2024
Could you still elaborate on what you mean with "not working"? Since the version of wee-slack that doesn't work with autosort isn't released yet, there is time to fix the problem before it hits the official script repository. But then I would really need to know what the problem is.
from weechat-autosort.
dyipon
commented on June 6, 2024
I just enabled the autosort.sorting.debug_log, and tried to get any error messages, but no success. No errors, no notices, the only thing I see is the channels are un-ordered.
I tried the manual /autosort, and got this: 'weechat | autosort: Finished sorting buffers in 0.0121 seconds.'
But buffer names remained in place.
A few lines from debug messages:
│0044 weechat | autosort: debug: Signal received during sort limit timeout, starting queued sort.
│0044 weechat | autosort: debug: Finished sorting buffers in 0.0482 seconds.
│0044 weechat | autosort: debug: Starting sort limit timeout of 100 ms.
│0044 weechat | autosort: debug: Sort limit timeout expired without receiving a signal.
│0044 weechat | autosort: debug: Signal buffer_renamed received, starting signal delay timeout of 5 ms.
│0044 weechat | autosort: debug: Signal delay timeout expired, starting sort.
│0044 weechat | autosort: debug: Finished sorting buffers in 0.0130 seconds.
│0044 weechat | autosort: debug: Starting sort limit timeout of 100 ms.
│0044 weechat | autosort: debug: Sort limit timeout expired without receiving a signal.
│0044 weechat | autosort: debug: Signal buffer_opened received, starting signal delay timeout of 5 ms.
│0044 weechat | autosort: debug: Signal delay timeout expired, starting sort.
│0044 weechat | autosort: debug: Finished sorting buffers in 0.0133 seconds.
│0044 weechat | autosort: debug: Starting sort limit timeout of 100 ms.
│0044 weechat | autosort: debug: Sort limit timeout expired without receiving a signal.
│0046 weechat | autosort: Finished sorting buffers in 0.0131 seconds.
│0046 weechat | autosort: Finished sorting buffers in 0.0132 seconds.
│0046 weechat | autosort: Finished sorting buffers in 0.0135 seconds.
│0046 weechat | autosort: debug: Signal buffer_opened received, starting signal delay timeout of 5 ms.
│- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
│0046 weechat | autosort: debug: Signal delay timeout expired, starting sort.
│0046 weechat | autosort: debug: Finished sorting buffers in 0.0135 seconds.
│0046 weechat | autosort: debug: Starting sort limit timeout of 100 ms.
│0046 weechat | autosort: debug: Sort limit timeout expired without receiving a signal.
│0047 weechat | autosort: Finished sorting buffers in 0.0127 seconds.
│0047 weechat | autosort: /autosort help: command not found
│0047 weechat | autosort: /autosort ?: command not found
│0047 weechat | autosort: Finished sorting buffers in 0.0121 seconds.
from weechat-autosort.
de-vri-es
commented on June 6, 2024
Thanks for the info. I suspect weeslack removed some buffer variables that are used for sorting. I will try to investigate.
from weechat-autosort.
de-vri-es
commented on June 6, 2024
I tested with the latest version from https://github.com/wee-slack/wee-slack and it still works as expected for me with the default rules.
Do you have non-default rules by any chance? If the problem persists, can post your rules and helper variables as shown by /autosort rules and /autosort helpers?
from weechat-autosort.
dyipon
commented on June 6, 2024
I just leeched the latest version of wee-slack, but no lock.
Here are my rules:
│0904 weechat | autosort: Sorting rules:
│0904 weechat | 0: ${if:${buffer.full_name}!=python.xxx.slack.com.#xx}
│0904 weechat | 1: ${if:${buffer.full_name}!=python.xxxx.slack.com.&xxxx}
│0904 weechat | 2: ${if:${buffer.full_name}!=irc.bitlbee.dogsie}
│0904 weechat | 3: ${if:${buffer.full_name}!=python.yyy.slack.com.yyy}
│0904 weechat | 4: ${if:${buffer.full_name}!=python.yyy.slack.com.tyyyy}
│0904 weechat | 5: ${if:${buffer.full_name}!=python.yyy.slack.com.&mobil}
│0906 weechat | autosort: Helper variables:
│0906 weechat | core_first: ${if:${buffer.full_name}!=core.weechat}
│0906 weechat | hashless_name: ${info:autosort_replace,#,,${buffer.name}}
│0906 weechat | irc_first: ${if:${buffer.plugin.name}!=irc}
│0906 weechat | irc_last: ${if:${buffer.plugin.name}==irc}
│0906 weechat | irc_raw_first: ${if:${buffer.full_name}!=irc.irc_raw}
│0906 weechat | irc_raw_last: ${if:${buffer.full_name}==irc.irc_raw}
from weechat-autosort.
de-vri-es
commented on June 6, 2024
Ah, I see. It looks like wee-slack renamed their buffers to python.slack.$workspace.$channel. The new naming scheme does seem more logical.
You'll have to update your custom rules to match.
from weechat-autosort.
dyipon
commented on June 6, 2024
Thanks for your help, It's working perfectly.
from weechat-autosort.
de-vri-es
commented on June 6, 2024
My pleasure, and glad to hear :)
from weechat-autosort.
Related Issues (16)
- Autosort will not sort my buffers by server properly HOT 10
- sorting by type - is it possible at all? HOT 13
- Buffers with spaces in the name HOT 2
- Plugin fails to load: AttributeError: 'str' object has no attribute 'decode' HOT 1
- Sorting an IRC channel after all other buffers results in odd behaviour. HOT 2
- Unicode characters in buffer names HOT 1
- Trying to sort my bitlbee stuff after everything else HOT 6
- scripts buffer can't be sorted HOT 4
- Default sort config does not support buffers with commas in their name HOT 2
- Sorting rules don't eval properly HOT 6
- on_info_replace getting called with not enough arguments HOT 7
- '/help autosort' missing explanation of newer '${info:}' options HOT 2
- Getting lots of these in my logs after recent host upgrade HOT 8
- Issues with custom sort when Slack channels are involved HOT 4
- Exception when running `/autosort helpers swap`
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from weechat-autosort.