Gnus development mailing list
 help / color / mirror / Atom feed
From: "Byung-Hee HWANG (황병희)" <soyeomul@doraji.xyz>
To: ding@gnus.org
Subject: Re: Custom Message-ID
Date: Thu, 18 Aug 2016 23:50:39 +0900	[thread overview]
Message-ID: <yw.87inuyqgg0.fsf@alex.chromebook> (raw)
In-Reply-To: <yu.86twemvtz2.fsf@student.uu.se> (Emanuel Berg's message of "Mon, 15 Aug 2016 19:10:25 +0200")

Emanuel Berg <embe8573@student.uu.se> 께서 쓰시길,
 《記事 全文 <yu.86twemvtz2.fsf@student.uu.se> 에서》:

> Byung-Hee HWANG "(황병희)" wrote:
>
>> Before i was struggling for finding it about
>> 15 hours. Anyway now i got it, solved it.
>> Thanks Emanuel^^ and you are elisp expert, it
>> is true;;
>
> Now let's think about this in all
> clear-headedness possible to upbring.
>
> In theory, there are no Elisp experts.
> There are only Lisp (or LISP) experts!
>
> In practice, I suppose the most experienced
> Emacs developers, e.g. [names removed by the
> anti-namedropping filter], are likewise Elisp
> and Lisp experts.

Very detailed. To non-expert like me, it is same so so both lisp and
elisp ^^;;

Thanks!

-- 
^고맙습니다 감사합니다_^))//



      reply	other threads:[~2016-08-18 14:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14 12:27 Byung-Hee HWANG (황병희)
2016-08-14 13:41 ` Eric Abrahamsen
2016-08-15 14:07   ` Byung-Hee HWANG (황병희)
2016-08-15 16:30     ` Ted Zlatanov
2016-08-15 17:12       ` Emanuel Berg
2016-08-15 17:07     ` Andreas Schwab
2016-08-15 17:15       ` Emanuel Berg
2016-08-15 17:27       ` Emanuel Berg
2016-08-17 11:58       ` Byung-Hee HWANG (황병희)
2016-08-18 14:23         ` Byung-Hee HWANG (황병희)
2016-08-15 13:59 ` Emanuel Berg
2016-08-15 14:31   ` Byung-Hee HWANG (황병희)
2016-08-15 17:10     ` Emanuel Berg
2016-08-18 14:50       ` Byung-Hee HWANG (황병희) [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=yw.87inuyqgg0.fsf@alex.chromebook \
    --to=soyeomul@doraji.xyz \
    --cc=ding@gnus.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 NNTP newsgroup(s).