unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: C-h r and Images
Date: Mon, 02 Sep 2013 23:01:36 +0530	[thread overview]
Message-ID: <878uzf5dvr.fsf@gmail.com> (raw)
In-Reply-To: <5224AEB3.5000508@cs.ucla.edu> (Paul Eggert's message of "Mon, 02 Sep 2013 08:28:51 -0700")


Sorry for multiple posts.  

I am banging my head over multiple accounts, posting styles and
X-Message-SMTP-Method etc.  Gnus is awesome only because I can edit my
mail within Emacs.  Otherwise it's just ...

Paul Eggert <eggert@cs.ucla.edu> writes:

> Eli Zaretskii wrote:
>>> > Is it because the Info browser doesn't support it.
>> Of course, it does!  Try reading the GnuTLS Info manual, for example.
>
> I just now tried that, and it didn't work for me.
> I visited (gnutls)TLS layers, and it said "[broken image]"
> instead of showing an image for Figure 3.1.  This is on
> Fedora 19 x86-64.

Works fine on Debian/Squeeze x86 and Emacs Bzr trunk.  

The package I installed is gnutls-doc.  I can see the image just fine,
if I do

    (info "(gnutls) TLS layers")

The header says this:

,----
| GNU TLS
| *******
| 
| This manual is last updated 2 June 2009 for version 2.8.6 of GNU TLS.
| 
| Copyright (C) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free
| Software Foundation, Inc.
`----

> Furthermore, images won't work well for users 

My motivation for the post was the thread in help list and a recurrent
confusion between a frame and a window.

It is easier to show 
 - a window
  - a frame
  - a minibuffer
  - a header line
  - a mode line 

with a single shot rather than explain it in Glossary.

Btw, looking at Glossary for Window, I am surprised that I don't know
what (q.v.) stands for.  The Emacs crowd *was* scholarly and academic
and it is to some extent even so today.  But using things like q.v. etc
and assuming that it will be understood by *lay* crowd is a bit too much
for the asking...

,----
| Window
|      Emacs divides a frame (q.v.) into one or more windows, each of
|      which can display the contents of one buffer (q.v.) at any time.
|      *Note Screen::, for basic information on how Emacs uses the screen.
|      *Note Windows::, for commands to control the use of windows.  Some
|      other editors use the term "window" for what we call a `frame'
|      (q.v.) in Emacs.
`----





  parent reply	other threads:[~2013-09-02 17:31 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 14:14 C-h r and Images Jambunathan K
2013-09-02 15:01 ` Eli Zaretskii
2013-09-02 15:28   ` Paul Eggert
2013-09-02 15:38     ` Eli Zaretskii
2013-09-02 15:40       ` Eli Zaretskii
2013-09-02 21:34         ` Paul Eggert
2013-09-03  2:43           ` Eli Zaretskii
2013-09-03  3:18             ` Stephen J. Turnbull
2013-09-09 10:03           ` Stephen Berman
2013-09-09 14:07             ` Stefan Monnier
2013-09-09 15:03               ` Stephen Berman
2013-09-09 15:01             ` Andreas Schwab
2013-09-09 15:06               ` Stephen Berman
2013-09-16 12:11             ` Per Starbäck
2013-09-02 16:11       ` Eli Zaretskii
2013-09-02 15:44     ` Drew Adams
2013-09-02 16:10       ` Eli Zaretskii
2013-09-02 17:31     ` Jambunathan K [this message]
2013-09-02 17:41       ` Eli Zaretskii
2013-09-02 18:34         ` Jambunathan K
2013-09-02 18:10       ` Drew Adams
2013-09-02 19:37         ` Juri Linkov
2013-09-02 20:16           ` Drew Adams
2013-09-03  2:37           ` Kanthimathi R
2013-09-03  8:56         ` Xue Fuqiao
2013-09-03 14:41           ` Drew Adams
2013-09-03 15:59           ` Eli Zaretskii
     [not found] <<87y57fe2ej.fsf@gmail.com>
     [not found] ` <<831u57e089.fsf@gnu.org>
     [not found]   ` <<5224AEB3.5000508@cs.ucla.edu>
     [not found]     ` <<4884857e-3cd1-4b47-9949-6919c60f2186@default>
     [not found]       ` <<83txi3cih5.fsf@gnu.org>
2013-09-02 17:02         ` Drew Adams
2013-09-02 17:39           ` Eli Zaretskii
     [not found]     ` <<878uzf5dvr.fsf@gmail.com>
     [not found]       ` <<50869c34-8cb2-477b-a6a8-a393abb76d12@default>
     [not found]         ` <<CAAF+z6EHgnt4Mbz8hHfv3csDUPYGvuNOQGKNB_AiNee7Umiahg@mail.gmail.com>
     [not found]           ` <<83ioyhdhg7.fsf@gnu.org>
2013-09-03 16:34             ` Drew Adams
2013-09-03 20:37               ` Juri Linkov
2013-09-04  5:47                 ` Eli Zaretskii
2013-09-04 22:38                 ` Xue Fuqiao
2013-09-04 22:41                   ` Xue Fuqiao
2013-09-05  7:07                   ` Eli Zaretskii
2013-09-06 10:53                     ` Xue Fuqiao
2013-09-06 12:16                       ` Eli Zaretskii
     [not found] <<372ba59c-42be-463c-a69f-6b910d8cc40e@default>
     [not found] ` <<83r4d7cecc.fsf@gnu.org>
2013-09-02 18:15   ` Drew Adams

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878uzf5dvr.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).