From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: Even though the HTML, man, markdown, PDF, PostScript, and tree
Date: Sat, 28 Mar 2020 11:19:13 -0500 (EST) [thread overview]
Message-ID: <11ff2ac58b96bbc3@mandoc.bsd.lv> (raw)
Log Message:
-----------
Even though the HTML, man, markdown, PDF, PostScript, and tree formatters
never write a ctags(1) file, using a pager still requires writing the
main output file and passing the file name to the pager.
Recent regression mentioned on IRC and reported by kn@.
Modified Files:
--------------
mandoc:
main.c
Revision Data
-------------
Index: main.c
===================================================================
RCS file: /home/cvs/mandoc/mandoc/main.c,v
retrieving revision 1.346
retrieving revision 1.347
diff -Lmain.c -Lmain.c -u -p -r1.346 -r1.347
--- main.c
+++ main.c
@@ -609,8 +609,7 @@ main(int argc, char *argv[])
(void)fchdir(startdir);
close(startdir);
}
- if (outst.outtype <= OUTT_UTF8)
- term_tag_finish();
+ term_tag_finish();
if (outst.outdata != NULL) {
switch (outst.outtype) {
case OUTT_HTML:
@@ -832,16 +831,14 @@ process_onefile(struct mparse *mp, struc
} else
fd = STDIN_FILENO;
- if (outst->outtype <= OUTT_UTF8) {
- if (outst->use_pager) {
- outst->use_pager = 0;
- outst->tag_files = term_tag_init(conf->output.tag);
- }
- if (outst->had_output) {
- if (outst->outdata == NULL)
- outdata_alloc(outst, &conf->output);
- terminal_sepline(outst->outdata);
- }
+ if (outst->use_pager) {
+ outst->use_pager = 0;
+ outst->tag_files = term_tag_init(conf->output.tag);
+ }
+ if (outst->had_output && outst->outtype <= OUTT_UTF8) {
+ if (outst->outdata == NULL)
+ outdata_alloc(outst, &conf->output);
+ terminal_sepline(outst->outdata);
}
if (resp->form == FORM_SRC)
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2020-03-28 16:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11ff2ac58b96bbc3@mandoc.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).