unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Ulf Jasper <ulf.jasper@web.de>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: newsticker-*.el files
Date: Tue, 10 Jun 2008 09:27:53 +0200	[thread overview]
Message-ID: <87k5gxsq9y.fsf@ambire.localdomain> (raw)
In-Reply-To: <84ve0iebry.fsf@web.de> (Ulf Jasper's message of "Mon, 09 Jun 2008 19:52:33 +0200")

[-- Attachment #1: Type: text/plain, Size: 764 bytes --]

() Ulf Jasper <ulf.jasper@web.de>
() Mon, 09 Jun 2008 19:52:33 +0200

   Probably it will be "nt".

Since newsticker handles other feed formats,
not just RSS, how about:

feedread
readfeed
rd-feed
feeddisp ("display")
feedshow
showfeed
feedtick
tickfeed
showxmlf (show XML (as opposed to some more elegant
                    sexp equivlant)
               feed)
etc, etc.

Personally, i prefer "showfeed", which can be shortened to "shfeed"
and then suffixed: "shfeed-x" (XML), shfeed-s (sexp), shfeeddN
(data acquisition -- think process monitoring -- format N), etc.

If you stretch a bit, another (further) stopping point is "tree":
"shtree".  I would be pleased to use such a facility for examining
gnugo.el runtime structures, for example.  Presently, `pp'


[-- Attachment #2: (http://www.gnuvola.org/software/j/gnugo/screenshots/2.png) --]
[-- Type: image/png, Size: 22485 bytes --]

[-- Attachment #3: Type: text/plain, Size: 33 bytes --]


and `describe-text-properties'


[-- Attachment #4: (http://www.gnuvola.org/software/j/gnugo/screenshots/3.png) --]
[-- Type: image/png, Size: 12397 bytes --]

[-- Attachment #5: Type: text/plain, Size: 121 bytes --]


work ok but are not as smooth as they could be.  Anyway,
probably if you rename it like Knuth would, you'll be ok!

thi

  parent reply	other threads:[~2008-06-10  7:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-08 18:22 newsticker-*.el files Eli Zaretskii
2008-06-08 22:01 ` Dan Nicolaescu
2008-06-08 23:44   ` David De La Harpe Golden
2008-06-09  8:13     ` Eli Zaretskii
2008-06-09  8:21       ` Miles Bader
2008-06-09  9:33         ` Juanma Barranquero
2008-06-08 23:44   ` Leo
2008-06-09  8:16     ` Eli Zaretskii
2008-06-09  8:23       ` Miles Bader
2008-06-09  9:12         ` Eli Zaretskii
2008-06-09  9:34           ` David Kastrup
2008-06-09  9:56             ` Juanma Barranquero
2008-06-09 23:15             ` Richard M Stallman
2008-06-09 23:45               ` Miles Bader
2008-06-10  3:25                 ` dhruva
2008-06-10 17:33                 ` Richard M Stallman
2008-06-09 17:22       ` Richard M Stallman
2008-06-09  0:30   ` Miles Bader
2008-06-09  1:49   ` Stefan Monnier
2008-06-09  8:23     ` Eli Zaretskii
2008-06-09 12:43       ` Dan Nicolaescu
2008-06-09 12:47         ` David Kastrup
2008-06-09 14:25           ` Eli Zaretskii
2008-06-09  8:06   ` Eli Zaretskii
2008-06-09  8:13     ` Miles Bader
2008-06-09  9:09       ` Eli Zaretskii
2008-06-09 13:35     ` Chong Yidong
     [not found] ` <84bq2beol7.fsf@web.de>
2008-06-09 17:52   ` Ulf Jasper
2008-06-09 18:19     ` Chong Yidong
2008-06-09 18:39       ` David Kastrup
2008-06-09 19:38         ` Ulf Jasper
2008-06-10  7:27     ` Thien-Thi Nguyen [this message]
2008-06-10 18:34       ` Ulf Jasper
2008-06-10 20:10         ` Eli Zaretskii
2008-06-11  8:06         ` Thien-Thi Nguyen
2008-06-12 19:05           ` Ulf Jasper
2008-06-12 19:52             ` Stefan Monnier
2008-06-12 20:30               ` Ulf Jasper
2008-06-13  8:23             ` Thien-Thi Nguyen

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=87k5gxsq9y.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=emacs-devel@gnu.org \
    --cc=ulf.jasper@web.de \
    /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).