unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: ken <gebser@mousecar.com>
To: Joost Kremers <joostkremers@yahoo.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: OT w/ misunderstanding Re: creating a sub-menu
Date: Tue, 12 Mar 2013 05:36:14 -0400	[thread overview]
Message-ID: <513EF70E.5070108@mousecar.com> (raw)
In-Reply-To: <slrnkjsd7a.ggb.joostkremers@j.kremers4.news.arnhem.chello.nl>

n 03/11/2013 03:47 PM Joost Kremers wrote:
> Hi Ken,
>
> ken wrote:
>> Joost,
>>
>> For some reason your replies (from the outset of this conversation)
>> aren't showing up as part of one and the same thread.
>
> I've been posting from two different computers, which may the the cause.

That by itself couldn't be the actual cause, not even should you be 
using different email programs on those two computers.  If you click 
"Reply"-- or for this particular list, "Reply All"-- the email program 
should maintain the threading of the conversation automatically for you 
(well, for all of us actually), regardless of which computer you do it 
on, regardless where on the internet those computers reside, etc.  This 
has been standard in email applications for a very long time.

In short, just click "Reply All" and everything should work fine.


>
>> On 03/06/2013 03:55 PM Joost Kremers wrote:
>> Thanks for responding, but no, none of that was at all helpful.  I still
>> want to create the sub-menu I originally described (the partial code for
>> which no longer exists in this thread) and so still would like
>> assistance formulating that code.
>
> I apologize for wasting your time. :-) To make up for it, I wanted to go
> and figure out why your code wasn't working, but it seems the answer has
> already been posted. Hope you get it working!

No need to apologize.  We're having a technical discussion, not a 
personal one.  It would help quite a bit in this regard though if, when 
you abridge the email you are replying to, the technical part of the 
discussion were not edited out.  Otherwise we're hearing the sound of 
one hand clapping.  If there's any doubt as to what's relevant, it would 
then be best just to leave the entirety of the quoted material intact.

Also, regarding "the answer", see my reply to Steve.



  reply	other threads:[~2013-03-12  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.21496.1362523165.855.help-gnu-emacs@gnu.org>
2013-03-06  1:42 ` creating a sub-menu Joost Kremers
2013-03-06 11:44   ` ken
     [not found]   ` <mailman.21539.1362570279.855.help-gnu-emacs@gnu.org>
2013-03-06 20:55     ` Joost Kremers
2013-03-07  9:36       ` OT w/ misunderstanding " ken
     [not found]       ` <mailman.21622.1362648982.855.help-gnu-emacs@gnu.org>
2013-03-11 19:47         ` Joost Kremers
2013-03-12  9:36           ` ken [this message]
     [not found]           ` <mailman.21918.1363080995.855.help-gnu-emacs@gnu.org>
2013-03-12 18:14             ` Joost Kremers

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=513EF70E.5070108@mousecar.com \
    --to=gebser@mousecar.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=joostkremers@yahoo.com \
    /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).