-
Notifications
You must be signed in to change notification settings - Fork 372
implement server-time #1108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement server-time #1108
Conversation
This comment has been minimized.
This comment has been minimized.
bcb1675
to
1b83caa
Compare
to try it, /set show_server_time on |
01d2e01
to
006fadf
Compare
7ab18e8
to
7e1a96a
Compare
@irssi/developers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this line meta / current_incoming_meta concept a lot, and the infrastructure you laid to make this possible. Thanks so much for working on this.
src/fe-text/textbuffer-formats.h
Outdated
@@ -3,6 +3,11 @@ | |||
|
|||
#include <irssi/src/fe-text/textbuffer.h> | |||
|
|||
typedef struct _TEXT_BUFFER_META_REC { | |||
gint64 server_time; | |||
GSList *next; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's this one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the meta will consist of pre-parsed meta-data like server_time (to be extended later, but keep in mind that this storage space is required for each line), and arbitrary generic meta-data in a list.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does that mean that next
will be always null for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
60a2c1b
to
b5f9bb2
Compare
I made a hash table implementation |
@dequis do you want to review this again? Now we have a tags parser and everything is hashes |
8c9f440
to
e864467
Compare
@irssi/developers |
Okay, okay, give me a few days. |
@dequis how many days do you want :)? |
Uhm. A few more? |
@dequis ping |
Damn time flies huh |
src/core/refstrings.h
Outdated
void i_refstr_release(char *str); | ||
#define i_refstr_release(str) ((str) == NULL ? NULL : g_ref_string_release(str)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds potentially bad? Having the name defined as both a function and a macro and needing an undef in refstrings.c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just make all of them functions then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, good idea, sounds more consistent from api/abi perspective too
I like this a lot! I tried really hard to find something to complain about to justify the time it took me to get around to this, and luckily I got something in the end. Phew. But yeah all good from architectural point of view. I'm a bit rusty on detecting memory bugs visually, we should just fuzz this stuff. |
thanks so much for your time and looking through it, much appreciated |
e864467
to
322df0d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 from the code review perspective, didn't do extra testing myself but we can do that after the merge
No description provided.