unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Yavor Doganov <yavor@gnu.org>
To: Adrian Robert <adrian.b.robert@gmail.com>
Cc: Yavor Doganov <yavor@gnu.org>, 1171@emacsbugs.donarmstrong.com
Subject: bug#1171: #1171 - ns-version-string - Emacs bug report logs
Date: Thu, 23 Oct 2008 02:20:04 +0300	[thread overview]
Message-ID: <87k5c0z07v.GNU's_Not_Unix!%yavor@gnu.org> (raw)
In-Reply-To: <0547AFB7-1140-479F-B9F7-87DC8349EBE9@gmail.com>

Adrian Robert wrote:
> 
> > Windowing system distributor `GNU', version  
> > 103.110.117.115.116.101.112.45.103.117.105.45.48.46.49.50.46.48
> 
> How do you generate this output?

With M-x report-emacs-bug -- I thought the whole point of this
discussion/bug was inluding useful information in initial bug reports,
without the necessity to ask the bug reporter about additional
details.

Anyway, I don't have strong feelings about this -- reporting the
gnustep-gui version is good enough.

> And do you know what code is responsible?

It's in lisp/mai/emacsbug.el.

> x-server-version should be returning identical to ns-version-string

That's wrong for GNUstep on a GNU/{Linux,Hurd,kFreeBSD} system where
presumably the desirable thing is to report the X server version (in
fact it would be much better to report the GNUstep backend, or both).
Furthermore, although GNUstep has minimal WM support and theoretically
Emacs.app can run under plain X (haven't tried that, personally), it
is a bit inappropriate to call GNU a "Windowing system distributor".
GNUstep provides some primitives, but really relies on X to be
available and running.

> If you could put a println in ns_appkit_version() in nsfns.m and see  
> if it IS indeed being called and if it IS generating that weird  
> string, it would help track it down.

Thanks, I'll hopefully do that tomorrow.






  reply	other threads:[~2008-10-22 23:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 13:31 bug#1171: #1171 - ns-version-string - Emacs bug report logs Adrian Robert
2008-10-21 15:52 ` Stefan Monnier
2008-10-21 22:37   ` Glenn Morris
2008-10-22 10:53     ` Yavor Doganov
2008-10-22 12:29       ` Adrian Robert
2008-10-22 13:14       ` Adrian Robert
2008-10-22 17:05         ` Glenn Morris
2008-10-22 21:11         ` Yavor Doganov
2008-10-22 22:43           ` Adrian Robert
2008-10-22 23:20             ` Yavor Doganov [this message]
2008-10-23  1:16             ` Stefan Monnier
2008-11-12 13:34               ` Yavor Doganov
2008-11-12 16:01                 ` Stefan Monnier
2008-11-12 19:11                   ` Yavor Doganov
2008-11-12 19:19                     ` Adrian Robert
2008-11-12 19:48                     ` Stefan Monnier
2008-12-11 23:46                       ` bug#1171: ns-version-string Glenn Morris
2008-12-31 15:03                         ` Adrian Robert
2008-10-23  1:02           ` bug#1171: #1171 - ns-version-string - Emacs bug report logs Glenn Morris
2008-10-23  0:48         ` Glenn Morris

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='87k5c0z07v.GNU'\''s_Not_Unix'\!'%yavor@gnu.org' \
    --to=yavor@gnu.org \
    --cc=1171@emacsbugs.donarmstrong.com \
    --cc=adrian.b.robert@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).