From: Xue Fuqiao <xfq.free@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: About "set bits"
Date: Fri, 12 Apr 2013 22:20:16 +0800 [thread overview]
Message-ID: <20130412222016.f8d7eae8bccfaaf64cb03c2f@gmail.com> (raw)
In-Reply-To: <87a9p44b2i.fsf@zigzag.favinet>
On Fri, 12 Apr 2013 06:39:17 +0200
Thien-Thi Nguyen <ttn@gnuvola.org> wrote:
> () Barry Margolin <barmar@alum.mit.edu>
> () Thu, 11 Apr 2013 11:19:54 -0400
>
> True, these phrases can be ambiguous. But often the context and
> examples help quite a bit in figuring out the intent. In this case,
> there were a couple of examples; "bits" tells you to think in binary,
> and if you examined the binary values of the examples it should
> quickly become apparent what was meant.
>
> Yes, i think if OP were to try more stuff in *scratch*, such questions
> could be avoided.
Agreed. Although I prefer *ielm*.
> In this case, i wrote examples that (to me) seem easy to inspect and
> mentally verify, so that *scratch* is not even necessary.
But I'm not familiar with binary files and binary code, I don't where to
start.
> Let's hope people will step forward and improve the docs over time.)
That's true. Although my English isn't very good, I'd be glad to
improve/refine the documentation for Emacs, like proof-reading the
manuals and adding documentation about some packages/features that
aren't mentioned in the manuals.
--
Xue Fuqiao
http://www.gnu.org/software/emacs/
prev parent reply other threads:[~2013-04-12 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 13:46 About "set bits" Xue Fuqiao
2013-04-10 14:15 ` Thien-Thi Nguyen
2013-04-10 15:20 ` Eli Zaretskii
[not found] ` <mailman.23883.1365607222.855.help-gnu-emacs@gnu.org>
2013-04-10 15:37 ` Barry Margolin
2013-04-10 22:33 ` Xue Fuqiao
2013-04-10 22:39 ` Xue Fuqiao
2013-04-11 8:46 ` Thien-Thi Nguyen
[not found] ` <mailman.23943.1365669842.855.help-gnu-emacs@gnu.org>
2013-04-11 15:19 ` Barry Margolin
2013-04-12 4:39 ` Thien-Thi Nguyen
2013-04-12 14:20 ` Xue Fuqiao [this message]
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=20130412222016.f8d7eae8bccfaaf64cb03c2f@gmail.com \
--to=xfq.free@gmail.com \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.