[tin-bugs] BUG REPORT tin 2.6.0 release 20210823 ("Coleburn") - saving an article takes about 4 seconds
Vincent Lefevre
vincent-news at vinc17.net
Thu Sep 23 13:40:32 CEST 2021
Version: tin 2.6.0 release 20210823 ("Coleburn") Sep 4 2021 09:41:27
Platform:
OS-Name = "linux-gnu"
Compiler:
CC = "gcc"
CFLAGS = "-g -g -O2 -ffile-prefix-map=/build/tin-URzr1H/tin-2.6.0=. -fstack-protector-strong -Wformat -Werror=format-security"
CPP = "gcc -E"
CPPFLAGS = "-Wdate-time -D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -D_XOPEN_SOURCE_EXTENDED"
Linker and Libraries:
LD = "gcc"
LDFLAGS = "-g -Wl,-z,relro"
LIBS = "-L/usr/lib -lpcre -lcanlock -lncursesw -ltinfo -luu -licuuc"
PCRE = "8.39 2016-06-14"
Characteristics:
+DEBUG +NNTP_ABLE -NO_POSTING -BROKEN_LISTGROUP +XHDR_XREF
-HAVE_FASCIST_NEWSADMIN +ENABLE_IPV6 -HAVE_COREFILE
-NO_SHELL_ESCAPE -DISABLE_PRINTING -DONT_HAVE_PIPING -NO_ETIQUETTE
+HAVE_LONG_FILE_NAMES +APPEND_PID +HAVE_MH_MAIL_HANDLING
+HAVE_ISPELL -HAVE_METAMAIL +HAVE_SUM
+HAVE_COLOR -HAVE_PGP -HAVE_PGPK +HAVE_GPG
+MIME_BREAK_LONG_LINES +MIME_STRICT_CHARSET +CHARSET_CONVERSION
+MULTIBYTE_ABLE -NO_LOCALE -USE_LONG_ARTICLE_NUMBERS
+USE_CANLOCK -EVIL_INSIDE -FORGERY -TINC_DNS -ENFORCE_RFC1034
-REQUIRE_BRACKETS_IN_DOMAIN_LITERAL -ALLOW_FWS_IN_NEWSGROUPLIST
BOX1 : Linux 5.14.0-1-amd64 (x86_64)
CFG1 : active=1800, arts=1200, reread=0, nntp_xover=OVER
CFG2 : debug=0, threading=2
CFG3 : domain=[/etc/mailname]
NNTP1: nntp.aioe.org InterNetNews NNRP server INN 2.6.1 ready (posting ok)
NNTP2: nntp.aioe.org InterNetNews NNRP server INN 2.6.1 ready (posting ok)
IMPLE: INN 2.6.1
Please enter _detailed_ bug report, gripe or comment:
Saving an article is very slow: about 4 seconds.
To reproduce:
1. Go to some article.
2. Type 's'.
3. At "Save a=article, t=thread, r=range, h=hot, p=pattern, T=tagged, q=quit"
type 'a'.
4. Choose '=' and type [Enter].
5. Hit the left arrow key.
After step 4, a message like
-- article saved to mailbox /home/vinc17/News/comp.std.c --
is displayed immediately, but I need to wait for about 4 seconds
before the left arrow is taken into account. I wonder what "tin"
is doing during this time... This may be
if (num_save == 1 || save[0].mailbox)
snprintf(buf, sizeof(buf), _(txt_saved_to),
what, (save[0].mailbox ? _(txt_mailbox) : ""), first);
else
snprintf(buf, sizeof(buf), _(txt_saved_to_range),
what, first, last);
wait_message((tinrc.beginner_level) ? 4 : 2, buf);
in feed.c, but why forcing to user to wait?
Note: if this is because there may be another displayed message
*without a user interaction*, then a delay could be introduced
only in this case.
--
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
More information about the tin-bugs
mailing list