unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tom Tromey <tromey@redhat.com>
Subject: java line termination
Date: 28 Jan 2003 11:30:47 -0700	[thread overview]
Message-ID: <874r7txh2g.fsf@fleche.redhat.com> (raw)

This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.2.1 (i386-redhat-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2002-04-08 on porky.devel.redhat.com
configured using `configure  i386-redhat-linux --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --with-gcc --with-pop --with-sound'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US.iso885915
  locale-coding-system: iso-latin-9
  default-enable-multibyte-characters: nil

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:


Java has its own rules for what constitutes a line terminator.

A bare \r is one, as is a bare \n; but the \r\n sequence is also
considered a single terminator.

I've run across Java source code which uses a mix of different line
terminators in a single file.  While ugly, there's not much I can do
about it.

If I compile code like this with gcj, and then use gdb to debug it, I
find that the debug arrow will be misplaced, because Emacs and gcj
disagree about the current line number.  Similarly, M-x next-error
will sometimes jump to the wrong line, as gcj reports line numbers
according to Java rules, but Emacs interprets them according to its
own rules.

I think in java-mode Emacs ought to respect Java's notion of line
termination.



Recent input:
l i k e SPC t h e r e ' s SPC m o r e SPC f o r SPC 
u s SPC t o SPC d o SPC h e r e SPC : - ( C-u C-b C-k 
l <backspace> , SPC b l e a h . C-p C-k C-e C-f C-f 
C-n C-f C-n C-f C-v C-c C-c M-v z C-c b C-v C-s j a 
v a C-w C-w C-w C-w C-s C-l C-s C-s C-s C-s C-s C-s 
C-s C-a M-x r e p o r t - e m <tab> <return>

Recent messages:
Saving file /home/tromey/.newsrc.eld...
Wrote /home/tromey/.newsrc.eld
Saving /home/tromey/.newsrc.eld...done
Mark set
set-mark-command: No mark set in this buffer [2 times]
Mark set [4 times]
Auto-saving...done
Sending...done

Mark saved where search started [2 times]

Tom

                 reply	other threads:[~2003-01-28 18:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=874r7txh2g.fsf@fleche.redhat.com \
    --to=tromey@redhat.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).