bug#71683: 30.0.50; Ellipsis buttons in compilation buffers can only be activated with the mouse

[Eli Zaretskii <eliz@gnu.org>]

> Date: Thu, 20 Jun 2024 23:41:01 +0000
> From: "Jose A. Ortega Ruiz" <mail@jao.io>
> Cc: Eli Zaretskii <eliz@gnu.org>
> 
> > I can reproduce the problem with this recipe, at least with my
> > configuration (haven't been able to try with emacs -Q yet):
> >
> > - M-x compile
> > - Enter as compile command:
> >
> > echo "21:27:16.195 ERROR wintermute.message.mailbox.rabbitmq-core -  -- ALARM -- Failure ack-ing {:error :exception, :code -20, :message \"An unexpected internal error occurred\", :info \"channel is already closed due to clean channel shutdown; protocol method: #method<channel.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)\", :trace (\"com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannjava:258)\" \"com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:427)\" \"com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:421)\" \"com.rabbitmq.client.impl.recovery.RecoveryAwareChannelN.basicAck(RecoveryAwareChannelN.java:93)\" \"com.rabbitmq.client.impl.recovery.AutorecoveringChannel.basicAck(AutorecoveringChannel.java:439)\" \"langohr.basic$ack.invokeStatic(basic.clj:205)\" \"langohr.basic$ack.invokePrim(basic.clj)\" \"wintermute.message.mailbox.rabbitmq_core$ack.invokeStatic(rabbitmq_core.clj:81)\" \"wintermute.message.mailbox.rabbitmq_core$ack.invoke(rabbitmq_core.clj:80)\" \"wintermute.message.mailbox.rabbitmq_core$consumer$ack__19911.invoke(rabbitmq_core.clj:89)\" \"wintermute.message.mailbox.rabbitmq_core$consumer$fn__19923$fn__19924.invoke(rabbitmq_core.clj:93)\" \"wintermute.delete.server$processor.invokeStatic(server.clj:229)\" \"wintermute.delete.server$processor.invoke(server.clj:221)\" \"clojure.core$partial$fn__5912.invoke(core.clj:2656)\" \"wintermute.message.mailbox.rabbitmq_core$consumer$fn__19923.invoke(rabbitmq_core.clj:93)\" \"langohr.consumers$create_default$fn__19833.invoke(consumers.clj:83)\" \"langohr.consumers.proxy$com.rabbitmq.client.DefaultConsumer$ff19274a.handleDelivery(Unknown Source)\" \"com.rabbitmq.client.impl.ConsumerDispatcher$5.run(ConsumerDispatcher.java:149)\" \"com.rabbitmq.client.impl.ConsumerWorkService$WorkPoolRunnable.run(ConsumerWorkService.java:104)\" \"java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\" \"java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\" \"java.base/java.lang.Thread.run(Thread.java:829)\")}"
> >
> > That produces a compilation buffer which ends in:
> >
> > 21:27:16.195 ERROR wintermute.message.mailbox.rabbitmq-core -  -- ALARM -- Failure ack-ing {:error :exception, :code -20, :message "An unexpected internal error occurred", :info "channel is already closed due to clean channel shutdown; protocol method: #method<channel.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)", :trace ("com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannjava:258)" "com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:427)" "com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:421)" "com.rabbitmq.client.impl.recovery.RecoveryAwareChannelN.basicAck(RecoveryAwareChannelN.java:93)" "com.rabbitmq.client.impl.recovery.AutorecoveringChannel.basicAck(AutorecoveringChannel.java:439)" "langohr.basic.invokeStatic(basic.clj:205)" "langohr.basic.invokePrim(basic.clj)" "wintermute.message.mailbox.rabbitmq_core.invokeStatic(rabbitmq_core.clj:81)" "wintermute.message.mailbox.rabbitmq_core.invoke(rabbitmq_core.clj:80)" "wintermute.message.mailbox.rabbitmq_core.invoke(rabbitmq_core.clj:89)" "wintermute.message.mailbox.rabbitmq_core.invoke(rabbitmq_core.clj:93)" "wintermute.delete.server.invokeStatic(server.clj:229)" "wintermute.delete.server.invoke(server.clj:221)" "clojure.core.invoke(core.clj:2656)" "wintermute.message.mailbox.rabbitmq_core.invoke(rabbitmq_core.clj:93)" "langohr.consumers.invoke(consumers.clj:83)" "langohr.consumers.proxy.rabbitmq.client.DefaultConsumer.handleDelivery(Unknown Source)" "com.rabbitmq.client.impl.ConsumerDispatcher.run(ConsumerDispatcher.java:149)" "com.rabbitmq.client.impl.ConsumerWorkService.run(ConsumerWorkService.java:104)" "java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)" "java.base/java.util.concurrent.ThreadPoolExecutor.run(ThreadPoolExecutor.java:628)" "java.base/java.lang.Thread.run(Thread.java:829)")}
> 
> Sorry, emacs tricked me and inserted the full message again. The
> compilation buffer looks in fact like this:
> 
> 21:27:16.195 ERROR wintermute.message.mailbox.rabbitmq-core -  -- ALARM -- Failure ack-ing {:error :exception, :code -20, :message "An unexpected internal error occurred", :info "channel is already closed due to clean channel shutdown; protocol method: #method<channel.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)", :trace ("com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannjava:258)" "com.rabbitmq.client.impl.AMQChannel.transmit(AMQCha[…]

So what is the problems you see with this?  If I go to the […] thing
(cursor is shown on the opening bracket) and press RET, Emacs asks me
where to find the file corresponding to this "error message".  Is this
what you wanted?  If not, what did you want to do?

The user option to disable this truncation does exist: it's
compilation-max-output-line-length.