From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: kawa@sourceware.org
Subject: 'images' directory for Info docs. Re: kawa 2.2 last call
Date: Sun, 16 Oct 2016 15:54:00 -0000 [thread overview]
Message-ID: <9590.1476633231@vereq.eip10.org> (raw)
In-Reply-To: Your message of "Fri, 14 Oct 2016 13:59:10 -0700." <cb82b1b2-c749-cdd5-820a-265577509ae4@bothner.com>
Minor: After a 'make install' I found that although kawa.info* files
were installed in the proper directory, the images subdirectory was not.
Once I copied it over manually, I could view the info pages for
'Composable pictures' with the embedded figures (nice!).
In case it matters: I did use a --prefix option to configure, in order
to install kawa in my user directory instead of system-wide.
Regards,
-chaw
next prev parent reply other threads:[~2016-10-16 15:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 20:59 Per Bothner
2016-10-14 23:39 ` David Pirotte
2016-10-14 23:45 ` Per Bothner
2016-10-15 0:17 ` David Pirotte
2016-10-15 0:38 ` Per Bothner
2016-10-15 20:56 ` Sudarshan S Chawathe
2016-10-15 21:03 ` Andrea Bernardini
2016-10-15 21:14 ` Per Bothner
2016-10-15 21:32 ` David Pirotte
2016-10-15 21:49 ` Per Bothner
2016-10-15 22:10 ` Per Bothner
2016-10-15 22:28 ` Andrea Bernardini
2016-10-15 23:05 ` Per Bothner
2016-10-15 23:19 ` Per Bothner
2016-10-15 23:39 ` Andrea Bernardini
2016-10-15 23:41 ` David Pirotte
2016-10-16 1:04 ` Per Bothner
2016-10-16 2:37 ` David Pirotte
2016-10-16 13:46 ` Debian Jessie success report. " Sudarshan S Chawathe
2016-10-16 0:09 ` Sudarshan S Chawathe
2016-10-16 1:17 ` Per Bothner
2016-10-16 1:51 ` Per Bothner
2016-10-15 22:40 ` Sudarshan S Chawathe
2016-10-15 21:10 ` Per Bothner
2016-10-15 21:22 ` Per Bothner
2016-10-15 21:58 ` Sudarshan S Chawathe
2016-10-15 22:23 ` makeinfo (version?) problem. " Sudarshan S Chawathe
2016-10-15 22:29 ` Per Bothner
2016-10-16 15:54 ` Sudarshan S Chawathe [this message]
2016-10-16 19:41 ` 'images' directory for Info docs. " Per Bothner
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=9590.1476633231@vereq.eip10.org \
--to=chaw@eip10.org \
--cc=kawa@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).