unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: nullx002 <nullx002@gmail.com>
Cc: 24292@debbugs.gnu.org
Subject: bug#24292: # Local Variables: not working
Date: Wed, 24 Aug 2016 11:21:22 +0000	[thread overview]
Message-ID: <20160824112121.GA4920@acm.fritz.box> (raw)
In-Reply-To: <87oa4ituj4.fsf@gmail.com>

On Wed, Aug 24, 2016 at 02:26:15PM +0530, nullx002 wrote:
> Alan Mackenzie <acm@muc.de> writes:

> initially i added LV using commands and that automatically added it at
> the bottom of the buffer/file and it didn't work in that case for both
> large and small files. but when i added those line manually by hand as
> you suggested it worked. (for both large and small files)

Glad to hear it!

> however there is a problem as i have to add extra top-level heading just
> above the LV block as to avoid it messing up with the org-drill and
> org-drill-table-generate i use to create :drill: for those org
> files. it works well for me now with :noexport: tag for that last
> heading for LV block. is there a better way to achieve what i am trying
> to do without adding a dummy header for LV block at the end of the file?

This is where your removal of the bug list address from the Cc: counts
against you.  I actually know nothing about org mode, but other people
reading the list actually know quite a lot.

However, I looked into the org mode manual, and see you can write
comments by starting a line with "#".  The "Local Variables:" line is
quite happy being after a comment marker, so you could write your LV
list entirely in org mode comments:

    # Local Variables:
    # ...
    # End:

> thanks for you quick reply it was very helpful.

Just one or two tips on getting quick help in the future.  Your post
would have been more appropriate on help-gnu-emacs@gnu.org, since it was
not clear that it was an actual Emacs bug.  (As it turned out, it
wasn't.)  Please, as already mentioned, leave in the list address when
you reply.  That way, more people get to see the problem, and there is a
complete record of the thread in the archives.

Anyways, I hope you can now get things sorted out, and continue being a
happy Emacs user.  :-)

-- 
Alan Mackenzie (Nuremberg, Germany).





      parent reply	other threads:[~2016-08-24 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 10:04 bug#24292: # Local Variables: not working nullx002
2016-08-23 17:00 ` Alan Mackenzie
     [not found]   ` <87oa4ituj4.fsf@gmail.com>
2016-08-24 11:21     ` Alan Mackenzie [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

  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=20160824112121.GA4920@acm.fritz.box \
    --to=acm@muc.de \
    --cc=24292@debbugs.gnu.org \
    --cc=nullx002@gmail.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.
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).