Aaron Matthis

```julia itmshowpw = @bind showpw CheckBox() ##next cell if showpw itmserverpassword = @bind serverpassword TextField(default=elem.password) else itmserverpassword = @bind serverpassword PasswordField(default=elem.password) end ##next cell elem.password = serverpassword ``` Currently I...

```julia function check_admin(client::Client, m::Message) guild = Discord.get_guild(client, m.guild_id) channel = Discord.get_channel(client, m.channel_id) perms = Discord.permissions_in(m.member, Discord.fetchval(guild), Discord.fetchval(channel)) return Discord.has_permission(perms, PERM_ADMINISTRATOR) end ``` that's the code which indirectly leads to that...

Given that I can't find the message_reference object, I guess that the newer developments of the discord api/gateway are not part of the library. :/

It's not the 0.7 but my current usage of `peco(identity)` as I was told in the slack thread. I'll reopen it but will try to redesign it to match how...

Now it might be ready to go, but I found that the visual history of what's been written previously just vanishes after the query. EDIT: Fixed tests

After force pushing like 5 times, I __MIGHT__ managed to fix everything. Who expects that tests are written with `setfield!` 😁 EDIT: `cat` is not a valid executable on windows...

Now 0.7 results in unsatisfiable constraints because peco_jll has constrained julia to be >=1. So maybe we should drop it now. But tbh why would anyone stay on 0.7?

Btw why there are no CI jobs for JL 1.2 and 1.3? (And soon 1.4)

> Did you see [#6 (comment)](https://github.com/tkf/InteractiveCodeSearch.jl/issues/6#issuecomment-574494692)? What do you think about implementing Option 2 here? I didn't see it. Regarding `CONFIG.interactive_matcher = ` we also could customize getproperty, though, as...

So what do you think about the get/setproperty function? Btw, removing `::Cmd` would be breaking then aswell because if for whatever reason someone decides to read that attribute he won't...