all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pawel <paulino90@tenbit.pl>
To: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: cperl does not create TAGS.
Date: Thu, 19 Jul 2007 10:14:18 +0200	[thread overview]
Message-ID: <18079.7514.549717.543906@localhost.localdomain> (raw)
In-Reply-To: <f7lqb0$31f$1@agate.berkeley.edu>

Ilya Zakharevich writes:
 > [A complimentary Cc of this posting was sent to
 > Pawel 
 > <paulino90@tenbit.pl>], who wrote in article <mailman.3535.1184602226.32220.help-gnu-emacs@gnu.org>:
 > > Hallo Group Members.
 > > 
 > > Perl->Tools->TAGS->Create Tags For Current File for current perl buffer creates almost empty TAGS file.
 > > Literally:
 > 
 > > my.perl.pl,0
 > > 
 > 
 > Pawel sent me some files, and I can reconstruct his problem - but only
 > if I run emacs -q (and, of course, (setq cperl-hairy t))!
 > 
 > Apparently, some bugs of Emacs are worked out in my (multi-megabyte)
 > Emacs-brain-damage-workarounds setup (to be honest, most of the volume
 > is workarounds about OLD damage - the setup should work starting with
 > v19.17 or some such).
 > 
 > Unfortunately, I have no time to investigate it any more; please
 > remind me in 10 days or so...
 > 
 > Thanks,
 > Ilya
 > _______________________________________________
 > help-gnu-emacs mailing list
 > help-gnu-emacs@gnu.org
 > http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

OK,
thanks alot
Pawel

  reply	other threads:[~2007-07-19  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3535.1184602226.32220.help-gnu-emacs@gnu.org>
2007-07-18  0:27 ` cperl does not create TAGS Ilya Zakharevich
2007-07-18 19:40 ` Ilya Zakharevich
2007-07-19  8:14   ` Pawel [this message]
2007-07-16 16:12 Pawel

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=18079.7514.549717.543906@localhost.localdomain \
    --to=paulino90@tenbit.pl \
    --cc=help-gnu-emacs@gnu.org \
    --cc=nospam-abuse@ilyaz.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.